From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+63cebbb27f598a7f901b@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org,
chouhan.shreyansh630@gmail.com, eadavis@qq.com, jack@suse.cz,
jeffm@suse.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
rkovhaev@gmail.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [reiserfs?] general protection fault in __fget_files (2)
Date: Thu, 15 Feb 2024 10:30:35 +0100 [thread overview]
Message-ID: <20240215093035.2xaftqkkgvtknc33@quack3> (raw)
In-Reply-To: <00000000000040a8cd061164b23a@google.com>
On Wed 14-02-24 21:14: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=16fbb3dc180000
> start commit: f5837722ffec Merge tag 'mm-hotfixes-stable-2023-12-27-15-0..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=da1c95d4e55dda83
> dashboard link: https://syzkaller.appspot.com/bug?extid=63cebbb27f598a7f901b
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1230c7e9e80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=133d189ae80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Looks sensible.
#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 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 9:54 [syzbot] [reiserfs?] general protection fault in __fget_files (2) syzbot
2024-02-15 5:14 ` syzbot
2024-02-15 9:30 ` 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=20240215093035.2xaftqkkgvtknc33@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=chouhan.shreyansh630@gmail.com \
--cc=eadavis@qq.com \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=rkovhaev@gmail.com \
--cc=syzbot+63cebbb27f598a7f901b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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).