From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+6e5f2db05775244c73b7@syzkaller.appspotmail.com>
Cc: achender@linux.vnet.ibm.com, achender@us.ibm.com,
adilger.kernel@dilger.ca, alex@clusterfs.com, axboe@kernel.dk,
brauner@kernel.org, jack@suse.cz, kernel@collabora.com,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
usama.anjum@collabora.com
Subject: Re: [syzbot] [ext4?] KASAN: out-of-bounds Read in ext4_ext_remove_space
Date: Mon, 12 Feb 2024 14:27:46 +0100 [thread overview]
Message-ID: <20240212132746.syu7dhttk7xsyhzp@quack3> (raw)
In-Reply-To: <000000000000690cfd06111b7ee6@google.com>
On Sun 11-02-24 05:54:02, 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=1764f648180000
> start commit: e6fda526d9db Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=1e3d5175079af5a4
> dashboard link: https://syzkaller.appspot.com/bug?extid=6e5f2db05775244c73b7
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a56679a80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d76b5da80000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Yes, the reproducer seems to be corrupting the image:
#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-12 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 11:50 [syzbot] [ext4?] KASAN: out-of-bounds Read in ext4_ext_remove_space syzbot
2023-09-07 12:56 ` Muhammad Usama Anjum
2023-09-07 13:27 ` Muhammad Usama Anjum
2024-02-11 13:54 ` syzbot
2024-02-12 13:27 ` 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=20240212132746.syu7dhttk7xsyhzp@quack3 \
--to=jack@suse.cz \
--cc=achender@linux.vnet.ibm.com \
--cc=achender@us.ibm.com \
--cc=adilger.kernel@dilger.ca \
--cc=alex@clusterfs.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+6e5f2db05775244c73b7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=usama.anjum@collabora.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