Control: severity -1 serious Hi Christoph,
Thanks for the quick feedback! On Thu, Oct 27, 2022 at 09:10:53PM +0200, Christoph Anton Mitterer wrote: > Am 27. Oktober 2022 20:56:49 MESZ schrieb Salvatore Bonaccorso > <car...@debian.org>: > >According to your references there is the workaround of mounting with > >clear_cache,space_cache=v2 and convert the filesystem. > > > >What would one prevent doing so? > > v2 space cache is still rather new and had only recently some bug > that could have caused catastrophic data corruption... so not > everyone might want to switch. > > Similarly, people may want to have these filesystems mounted with > older kernels, whose v2 support isn't that good yet. Thanks, this is very important input. > >I'm downgrading the severity to important as it does not make the > >kernel unbootable or unstable on common hardware or all systems that a > >flavour is supposed to support. > > But now it a) migrates to testing an possibly leaves even more > systems with an unbootable system... b) with severity important, > people using e.g. apr-listbugs won't see it. > > OTOH, fixing the CVE is of course important, too. I did decide to still do so, so we can have the CVE fix migrate finally to testing (which took some time as well given there was the perl transition ongoing). I did import already 6.0.5 and will upload next so we get the btrfs fix. And I have made the bug now as well again back RC severity. Thank you! Regards, Salvatore
