From: syzbot <syzbot+7ca256d0da4af073b2e2@syzkaller.appspotmail.com>
To: anders.roxell@linaro.org, arnd@arndb.de, brauner@kernel.org,
frank.li@vivo.com, glaubitz@physik.fu-berlin.de,
gregkh@linuxfoundation.org, kstewart@linuxfoundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
pombredanne@nexb.com, slava@dubeyko.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
yepeilin.cs@gmail.com
Subject: Re: [syzbot] [hfs?] general protection fault in hfs_find_init
Date: Fri, 05 Sep 2025 22:56:03 -0700 [thread overview]
Message-ID: <68bbccf3.a70a0220.7a912.02c1.GAE@google.com> (raw)
In-Reply-To: <94eb2c0b816ebcae030568bb756a@google.com>
syzbot suspects this issue was fixed by commit:
commit 42b0ef01e6b5e9c77b383d32c25a0ec2a735d08a
Author: Arnd Bergmann <arnd@arndb.de>
Date: Fri Jul 11 08:46:51 2025 +0000
block: fix FS_IOC_GETLBMD_CAP parsing in blkdev_common_ioctl()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17c0d312580000
start commit: ee88bddf7f2f Merge tag 'bpf-fixes' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=28cc6f051378bb16
dashboard link: https://syzkaller.appspot.com/bug?extid=7ca256d0da4af073b2e2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1026b182580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159e0f0c580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: block: fix FS_IOC_GETLBMD_CAP parsing in blkdev_common_ioctl()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-06 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 20:47 general protection fault in hfs_find_init syzbot
2025-09-06 5:56 ` syzbot [this message]
2025-09-06 6:21 ` [syzbot] [hfs?] " Arnd Bergmann
2025-10-15 14:01 ` Tetsuo Handa
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=68bbccf3.a70a0220.7a912.02c1.GAE@google.com \
--to=syzbot+7ca256d0da4af073b2e2@syzkaller.appspotmail.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=slava@dubeyko.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=yepeilin.cs@gmail.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