From: syzbot <syzbot+60864ed35b1073540d57@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, alden.tondettar@gmail.com,
axboe@kernel.dk, brauner@kernel.org, dvyukov@google.com,
hch@infradead.org, hdanton@sina.com, jack@suse.com,
jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, pali@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [udf?] KASAN: use-after-free Write in udf_close_lvid
Date: Sun, 18 Feb 2024 10:20:04 -0800 [thread overview]
Message-ID: <000000000000aaf29f0611ac0603@google.com> (raw)
In-Reply-To: <00000000000056e02f05dfb6e11a@google.com>
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=12c941c2180000
start commit: f016f7547aee Merge tag 'gpio-fixes-for-v6.7-rc8' of git://..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f8e72bae38c079e4
dashboard link: https://syzkaller.appspot.com/bug?extid=60864ed35b1073540d57
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c2caf9e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11f518f9e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Block writes to mounted block devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-02-18 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 0:17 [syzbot] KASAN: use-after-free Write in udf_close_lvid syzbot
2022-05-24 10:32 ` Jan Kara
2022-05-24 10:46 ` Pali Rohár
2022-05-24 11:37 ` Jan Kara
2022-05-24 14:43 ` Dmitry Vyukov
2024-02-18 18:20 ` syzbot [this message]
2024-02-19 11:51 ` [syzbot] [udf?] " Jan Kara
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=000000000000aaf29f0611ac0603@google.com \
--to=syzbot+60864ed35b1073540d57@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=alden.tondettar@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dvyukov@google.com \
--cc=hch@infradead.org \
--cc=hdanton@sina.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.org \
--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 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 NNTP newsgroup(s).