From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+3f6ef04b7cf85153b528@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, jack@suse.cz,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
reiserfs-devel@vger.kernel.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] BUG: unable to handle kernel paging request in reiserfs_readdir_inode
Date: Thu, 15 Feb 2024 14:21:19 +0100 [thread overview]
Message-ID: <20240215132119.gtxttrj3jsft2hwe@quack3> (raw)
In-Reply-To: <00000000000018f2c806116ae6d3@google.com>
On Thu 15-02-24 04:38:04, 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=14ffd320180000
> start commit: 534293368afa Merge tag 'kbuild-fixes-v6.3' of git://git.ke..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=9688428cfef5e8d5
> dashboard link: https://syzkaller.appspot.com/bug?extid=3f6ef04b7cf85153b528
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=138d82bac80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1123fed2c80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Frankly I don't see the reproducer doing anything suspicious but since we
have no reproducer and this is reiserfs:
#syz fix: fs: Block writes to mounted block devices
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-02-15 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 19:12 [syzbot] [reiserfs?] [jfs?] BUG: unable to handle kernel paging request in reiserfs_readdir_inode syzbot
2023-03-18 20:21 ` [syzbot] [reiserfs?] " syzbot
2024-02-15 12:38 ` syzbot
2024-02-15 13:21 ` 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=20240215132119.gtxttrj3jsft2hwe@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+3f6ef04b7cf85153b528@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 read-only IMAP folder(s) and NNTP newsgroup(s).