From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+9cf75dc581fb4307d6dd@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, axboe@kernel.dk, brauner@kernel.org,
ebiggers@google.com, ebiggers@kernel.org, jack@suse.cz,
krisman@collabora.com, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, twuufnxlz@gmail.com,
tytso@mit.edu
Subject: Re: [syzbot] [ext4?] general protection fault in utf8nlookup
Date: Tue, 13 Feb 2024 11:42:18 +0100 [thread overview]
Message-ID: <20240213104218.utvf3t2abfgqdhbb@quack3> (raw)
In-Reply-To: <000000000000600b5d06113869f0@google.com>
On Mon 12-02-24 16:24:03, 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=17547fd4180000
> start commit: e42bebf6db29 Merge tag 'efi-fixes-for-v6.6-1' of git://git..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=df91a3034fe3f122
> dashboard link: https://syzkaller.appspot.com/bug?extid=9cf75dc581fb4307d6dd
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1374a174680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b12928680000
>
> If the result looks correct, please mark the issue as fixed by replying with:
The reproducer definitely does weird stuff like mmapping the loop device.
So 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-02-13 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 5:25 [syzbot] [ext4?] general protection fault in utf8nlookup syzbot
2023-09-20 7:36 ` Eric Biggers
2023-09-20 11:20 ` [PATCH] unicode: add s_encoding null ptr check in utf8ncursor Edward AD
2023-09-20 19:37 ` Eric Biggers
2024-02-13 0:24 ` [syzbot] [ext4?] general protection fault in utf8nlookup syzbot
2024-02-13 10:42 ` 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=20240213104218.utvf3t2abfgqdhbb@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ebiggers@google.com \
--cc=ebiggers@kernel.org \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9cf75dc581fb4307d6dd@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=twuufnxlz@gmail.com \
--cc=tytso@mit.edu \
/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