From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+4654552e088ed458b10d@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] BUG: unable to handle kernel NULL pointer dereference in reiserfs_find_entry
Date: Wed, 31 Jan 2024 18:18:45 +0100 [thread overview]
Message-ID: <20240131171845.okzidcm6gylcy4gw@quack3> (raw)
In-Reply-To: <000000000000e3d3f9061040b2ff@google.com>
On Wed 31-01-24 08:52:05, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@suse.cz>
> Date: Wed Nov 1 17:43:10 2023 +0000
>
> fs: Block writes to mounted block devices
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17e6fb5be80000
> start commit: 51f269a6ecc7 Merge tag 'probes-fixes-6.4-rc4' of git://git..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=162cf2103e4a7453
> dashboard link: https://syzkaller.appspot.com/bug?extid=4654552e088ed458b10d
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1177c895280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f4b2a5280000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Makes sense:
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-01-31 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 6:04 [syzbot] BUG: unable to handle kernel NULL pointer dereference in reiserfs_find_entry syzbot
2023-02-13 23:40 ` [syzbot] [reiserfs?] " syzbot
2024-01-31 16:52 ` syzbot
2024-01-31 17:18 ` Jan Kara [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=20240131171845.okzidcm6gylcy4gw@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzbot+4654552e088ed458b10d@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).