From: syzbot <syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com>
To: 20230801155823.206985-1-ghandatmanas@gmail.com,
88c258bd-3d0c-de79-b411-6552841eb8d0@gmail.com, axboe@kernel.dk,
brauner@kernel.org, ghandatmanas@gmail.com,
gregkh@linuxfoundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, luisbg@kernel.org,
salah.triki@gmail.com, syzkaller-bugs@googlegroups.com,
syzkaller@googlegroups.com, w@1wt.eu
Subject: Re: [syzbot] [fs?] UBSAN: shift-out-of-bounds in befs_check_sb
Date: Sun, 03 Mar 2024 00:30:05 -0800 [thread overview]
Message-ID: <00000000000080f93d0612bd6a5e@google.com> (raw)
In-Reply-To: <000000000000c29dab06004a752b@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=14b5e754180000
start commit: 8689f4f2ea56 Merge tag 'mmc-v6.5-2' of git://git.kernel.or..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=15873d91ff37a949
dashboard link: https://syzkaller.appspot.com/bug?extid=fc26c366038b54261e53
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14237dc2a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e34d22a80000
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
parent reply other threads:[~2024-03-03 8:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000c29dab06004a752b@google.com>]
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=00000000000080f93d0612bd6a5e@google.com \
--to=syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com \
--cc=20230801155823.206985-1-ghandatmanas@gmail.com \
--cc=88c258bd-3d0c-de79-b411-6552841eb8d0@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ghandatmanas@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@kernel.org \
--cc=salah.triki@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
--cc=w@1wt.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).