On Mon, Dec 7, 2020 at 10:34 AM syzbot <syzbot+c4b1e5278d93269fd...@syzkaller.appspotmail.com> wrote: > > syzbot suspects this issue was fixed by commit: > > commit 0697d9a610998b8bdee6b2390836cb2391d8fd1a > Author: Johannes Thumshirn <johannes.thumsh...@wdc.com> > Date: Wed Nov 18 09:03:26 2020 +0000 > > btrfs: don't access possibly stale fs_info data for printing duplicate > device > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10fb0d9b500000 > start commit: 521b619a Merge tag 'linux-kselftest-kunit-fixes-5.10-rc3' .. > git tree: upstream > kernel config: https://syzkaller.appspot.com/x/.config?x=e791ddf0875adf65 > dashboard link: https://syzkaller.appspot.com/bug?extid=c4b1e5278d93269fd69c > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16296f5c500000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1614e746500000 > > If the result looks correct, please mark the issue as fixed by replying with: > > #syz fix: btrfs: don't access possibly stale fs_info data for printing > duplicate device > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz fix: btrfs: don't access possibly stale fs_info data for printing duplicate device
