Thanks! 5.3.7 hit my system from the Fedora repos just a day or two after my last mail, and spent last evening trying to reproduce both the problem the scripts shows, but also the problem I tried to track down when making the script. Both seems to be gone after upgrading on the systems I have been able to run the test on so far. Best Regards, Peter hjalmarsson Den mån 28 okt. 2019 kl 08:50 skrev Johannes Thumshirn <jthumshirn@xxxxxxx>: > > On 27/10/2019 14:24, Su Yue wrote: > [...] > > > > Interesting thing I met too. That's not reproducible on my VM but > > host (Archlinux v5.3.6 same kernel config). > > > > What's more interesting is that v5.3.7 seems to have fixed the bug. > > After some bisect. The commit is > > > > commit 417d26300214f7b593a99c6bc8badb66492ae322 > > Author: Qu Wenruo <wqu@xxxxxxxx> > > Date: Mon Sep 23 14:56:14 2019 +0800 > > > > btrfs: relocation: fix use-after-free on dead relocation roots > > > > commit 1fac4a54374f7ef385938f3c6cf7649c0fe4f6cd upstream. > > > > Good catch, cherry-picking this commit on top of v5.3.5 resolves the > issue in my setup. > > -- > Johannes Thumshirn SUSE Labs Filesystems > jthumshirn@xxxxxxx +49 911 74053 689 > SUSE Software Solutions Germany GmbH > Maxfeldstr. 5 > 90409 Nürnberg > Germany > (HRB 36809, AG Nürnberg) > Geschäftsführer: Felix Imendörffer > Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
