From: syzbot <syzbot+aded2f2ab94d81727898@syzkaller.appspotmail.com>
To: aik@ozlabs.ru, akpm@linux-foundation.org, axboe@kernel.dk,
hch@lst.de, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mingo@kernel.org, mingo@redhat.com, peterz@infradead.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
will@kernel.org
Subject: Re: KASAN: null-ptr-deref Write in bdi_put
Date: Mon, 01 Mar 2021 04:56:07 -0800 [thread overview]
Message-ID: <00000000000030504905bc792423@google.com> (raw)
In-Reply-To: <0000000000002525c205b604547a@google.com>
syzbot suspects this issue was fixed by commit:
commit 2d2f6f1b4799428d160c021dd652bc3e3593945e
Author: Christoph Hellwig <hch@lst.de>
Date: Thu Jan 7 18:36:40 2021 +0000
block: pre-initialize struct block_device in bdev_alloc_inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1424a5b6d00000
start commit: 71c061d2 Merge tag 'for-5.11-rc2-tag' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=33b7f56c5bf0f684
dashboard link: https://syzkaller.appspot.com/bug?extid=aded2f2ab94d81727898
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143f7fc0d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1089023f500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: block: pre-initialize struct block_device in bdev_alloc_inode
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-03-01 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 9:03 KASAN: null-ptr-deref Write in bdi_put syzbot
2021-03-01 12:56 ` syzbot [this message]
2021-03-01 14:35 ` Jens Axboe
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=00000000000030504905bc792423@google.com \
--to=syzbot+aded2f2ab94d81727898@syzkaller.appspotmail.com \
--cc=aik@ozlabs.ru \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.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).