From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz,
syzbot <syzbot+582e66e5edf36a22c7b0@syzkaller.appspotmail.com>,
clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in btrfs_scan_one_device
Date: Wed, 30 Sep 2020 20:05:22 +0200 [thread overview]
Message-ID: <20200930180522.GR6756@twin.jikos.cz> (raw)
In-Reply-To: <20200930165756.GQ6756@twin.jikos.cz>
On Wed, Sep 30, 2020 at 06:57:56PM +0200, David Sterba wrote:
> On Sun, Sep 20, 2020 at 07:12:14AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: eb5f95f1 Merge tag 's390-5.9-6' of git://git.kernel.org/pu..
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=10a0a8bb900000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=ffe85b197a57c180
> > dashboard link: https://syzkaller.appspot.com/bug?extid=582e66e5edf36a22c7b0
> > compiler: gcc (GCC) 10.1.0-syz 20200507
> >
> > Unfortunately, I don't have any reproducer for this issue yet.
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+582e66e5edf36a22c7b0@syzkaller.appspotmail.com
>
> #syz fix: btrfs: fix overflow when copying corrupt csums for a message
Johannes spotted that this is not the right fix for this report, I don't
know how to tell syzbot to revert the 'fix:' command, there isn't
'unfix' (like there's 'undup').
next prev parent reply other threads:[~2020-09-30 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 14:12 KASAN: use-after-free Read in btrfs_scan_one_device syzbot
2020-09-21 5:38 ` syzbot
2020-09-21 8:22 ` Johannes Thumshirn
2020-09-21 8:53 ` Johannes Thumshirn
2020-09-21 8:53 ` syzbot
2020-09-21 8:53 ` syzbot
2020-09-30 16:57 ` David Sterba
2020-09-30 18:05 ` David Sterba [this message]
2020-10-01 13:05 ` Dmitry Vyukov
2020-10-01 13:08 ` Dmitry Vyukov
2020-10-01 13:35 ` David Sterba
2020-10-12 20:56 ` Rustam Kovhaev
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=20200930180522.GR6756@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+582e66e5edf36a22c7b0@syzkaller.appspotmail.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 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).