From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+d8fc21bfa138a5ae916d@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, jack@suse.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] KASAN: use-after-free Read in crc_itu_t
Date: Fri, 26 Jan 2024 15:11:00 +0100 [thread overview]
Message-ID: <20240126141100.s6hphczfikjbbrm5@quack3> (raw)
In-Reply-To: <000000000000d227b6060fd90a48@google.com>
On Fri 26-01-24 05:12: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=1204f1efe80000
> start commit: a4d7d7011219 Merge tag 'spi-fix-v6.4-rc5' of git://git.ker..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=7474de833c217bf4
> dashboard link: https://syzkaller.appspot.com/bug?extid=d8fc21bfa138a5ae916d
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1442e70b280000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16db80dd280000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Looks good:
#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-26 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 14:28 [syzbot] KASAN: use-after-free Read in crc_itu_t syzbot
2022-10-21 19:43 ` syzbot
2024-01-26 13:12 ` [syzbot] [udf?] " syzbot
2024-01-26 14:11 ` 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=20240126141100.s6hphczfikjbbrm5@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d8fc21bfa138a5ae916d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.