From: syzbot <syzbot+c4b1e5278d93269fd69c@syzkaller.appspotmail.com>
To: anand.jain@oracle.com, clm@fb.com, dsterba@suse.com,
johannes.thumshirn@wdc.com, josef@toxicpanda.com,
jthumshirn@suse.de, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, nborisov@suse.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in btrfs_scan_one_device
Date: Mon, 07 Dec 2020 01:34:03 -0800 [thread overview]
Message-ID: <000000000000e0aa9a05b5dc86cb@google.com> (raw)
In-Reply-To: <0000000000002ae6eb05b3bd420c@google.com>
syzbot suspects this issue was fixed by commit:
commit 0697d9a610998b8bdee6b2390836cb2391d8fd1a
Author: Johannes Thumshirn <johannes.thumshirn@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
next prev parent reply other threads:[~2020-12-07 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 9:25 KASAN: slab-out-of-bounds Read in btrfs_scan_one_device syzbot
2020-12-07 9:34 ` syzbot [this message]
2020-12-07 9:50 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000e0aa9a05b5dc86cb@google.com \
--to=syzbot+c4b1e5278d93269fd69c@syzkaller.appspotmail.com \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.