From: syzbot <syzbot+d2dd123304b4ae59f1bd@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, clm@fb.com, dsterba@suse.com,
hch@lst.de, josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] KASAN: use-after-free Read in copy_page_from_iter_atomic (2)
Date: Fri, 10 Jun 2022 00:10:19 -0700 [thread overview]
Message-ID: <00000000000085068105e112a117@google.com> (raw)
In-Reply-To: <0000000000003ce9d105e0db53c8@google.com>
syzbot has bisected this issue to:
commit 4cd4aed63125ccd4efc35162627827491c2a7be7
Author: Christoph Hellwig <hch@lst.de>
Date: Fri May 27 08:43:20 2022 +0000
btrfs: fold repair_io_failure into btrfs_repair_eb_io_failure
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1332525ff00000
start commit: ff539ac73ea5 Add linux-next specific files for 20220609
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10b2525ff00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1732525ff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a5002042f00a8bce
dashboard link: https://syzkaller.appspot.com/bug?extid=d2dd123304b4ae59f1bd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d6d7cff00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1113b2bff00000
Reported-by: syzbot+d2dd123304b4ae59f1bd@syzkaller.appspotmail.com
Fixes: 4cd4aed63125 ("btrfs: fold repair_io_failure into btrfs_repair_eb_io_failure")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-06-10 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 13:11 [syzbot] KASAN: use-after-free Read in copy_page_from_iter_atomic (2) syzbot
2022-06-10 1:24 ` syzbot
2022-06-10 7:10 ` syzbot [this message]
2022-06-13 19:39 ` David Sterba
2022-06-14 7:17 ` Christoph Hellwig
2022-06-14 8:50 ` Qu Wenruo
2022-06-15 13:21 ` Christoph Hellwig
2022-06-15 21:27 ` Qu Wenruo
2022-06-16 6:35 ` Christoph Hellwig
2022-06-16 14:57 ` David Sterba
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=00000000000085068105e112a117@google.com \
--to=syzbot+d2dd123304b4ae59f1bd@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).