From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+82df44ede2faca24c729@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, groeck@google.com,
hdanton@sina.com, jack@suse.com, jack@suse.cz,
kernel@collabora.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, shreeya.patel@collabora.com,
steve.magnani@digidescorp.com, steve@digidescorp.com,
syzkaller-bugs@googlegroups.com, zsm@google.com
Subject: Re: [syzbot] [udf?] KASAN: use-after-free Read in udf_sync_fs
Date: Thu, 1 Feb 2024 10:14:18 +0100 [thread overview]
Message-ID: <20240201091418.rqapa3fbc563jeyk@quack3> (raw)
In-Reply-To: <000000000000d33080061046ed47@google.com>
On Wed 31-01-24 16:18: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=11282540180000
> start commit: 55cb5f43689d Merge tag 'trace-v6.7-rc6' of git://git.kerne..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=e5751b3a2226135d
> dashboard link: https://syzkaller.appspot.com/bug?extid=82df44ede2faca24c729
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12dbd63ee80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1534bed1e80000
>
> 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
next prev parent reply other threads:[~2024-02-01 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 10:09 syzbot
2023-08-14 20:07 ` syzbot
2024-02-01 0:18 ` syzbot
2024-02-01 9:14 ` Jan Kara [this message]
[not found] <20230813010800.1071-1-hdanton@sina.com>
2023-08-13 1:34 ` syzbot
[not found] <20230813020336.1128-1-hdanton@sina.com>
2023-08-13 2:41 ` syzbot
[not found] <20230813074848.1185-1-hdanton@sina.com>
2023-08-13 8:45 ` syzbot
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=20240201091418.rqapa3fbc563jeyk@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=groeck@google.com \
--cc=hdanton@sina.com \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shreeya.patel@collabora.com \
--cc=steve.magnani@digidescorp.com \
--cc=steve@digidescorp.com \
--cc=syzbot+82df44ede2faca24c729@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zsm@google.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
all inboxes | Powered by JetHome®