From: syzbot <syzbot+b8d61a58b7c7ebd2c8e0@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk, hch@lst.de,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, minchan@kernel.org,
reiserfs-devel@vger.kernel.org, senozhatsky@chromium.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [reiserfs?] KASAN: user-memory-access Write in zram_slot_lock
Date: Tue, 23 May 2023 02:34:31 -0700 [thread overview]
Message-ID: <00000000000026bdd305fc5918a5@google.com> (raw)
In-Reply-To: <00000000000066a94205fc488445@google.com>
syzbot has bisected this issue to:
commit 9fe95babc7420722d39a1ded379027a1e1825d3a
Author: Christoph Hellwig <hch@lst.de>
Date: Tue Apr 11 17:14:44 2023 +0000
zram: remove valid_io_request
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132fa586280000
start commit: 44c026a73be8 Linux 6.4-rc3
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10afa586280000
console output: https://syzkaller.appspot.com/x/log.txt?x=172fa586280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7d8067683055e3f5
dashboard link: https://syzkaller.appspot.com/bug?extid=b8d61a58b7c7ebd2c8e0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1223f7d9280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1245326a280000
Reported-by: syzbot+b8d61a58b7c7ebd2c8e0@syzkaller.appspotmail.com
Fixes: 9fe95babc742 ("zram: remove valid_io_request")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-05-23 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 13:47 [syzbot] [block?] [reiserfs?] KASAN: user-memory-access Write in zram_slot_lock syzbot
2023-05-23 9:34 ` syzbot [this message]
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=00000000000026bdd305fc5918a5@google.com \
--to=syzbot+b8d61a58b7c7ebd2c8e0@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).