From cc4a69858f4a13bdb5cc2408979f16e82a426498 Mon Sep 17 00:00:00 2001 From: Thomas Schoebel-Theuer Date: Sat, 2 Mar 2019 22:33:13 +0100 Subject: [PATCH] all: release mars0.1astable70 --- ChangeLog | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/ChangeLog b/ChangeLog index 156907ed..c7188e68 100644 --- a/ChangeLog +++ b/ChangeLog @@ -153,6 +153,32 @@ Changelog for series 0.1a: Now stable. Receive mainly fixes. +mars0.1astable70 (merged from mars0.1stable70) + * Critical fix: a few upper-layer kernel components are + allocating struct bio on the stack. This led to stack memory + corruption. If you ever had this problem, you certainly have + noticed it ;) Thus it should not have affected your data. + Unfortunately, I got no bug reports about this for several years. + Discovered when testing compatibility to very new kernels, + and now hopefully fixed. + * Major fixes: the systemd interface was not in a mature state. + Now improved a lot. More improvements are likely to follow + in the next months. + * Minor clarification: build for ancient kernel 2.6.32 was broken. + Fixing the build was no problem, but then the resulting kernel + deadlocked in certain situations (sb_mount mutex and sisters). + The reason is that stacking of filesystem instances (like + /vol/mydata relying on IO to /mars) is a pain in the very old + kernel architecture. + Any upstream kernel before 3.16 is EOL right now. Nevertheless, + I am officially supporting 3.2 at the moment, and have tested it. + Anyway, productive use of ancient kernels is not + recommended, for various reasons. + Notice that you also need old gcc versions for building such + EOL kernels. + Thus I decided to remove support for 2.6.32 officially. + If somebody needs it _really_, please contact me. + mars0.1astable69 (merged from mars0.1stable69) * Major improvement: compatibility to upstream kernel 4.9.x.