From: syzbot <syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xandfury@gmail.com
Subject: Re: [syzbot] [fs?] UBSAN: shift-out-of-bounds in befs_check_sb
Date: Sun, 28 Sep 2025 12:53:02 -0700 [thread overview]
Message-ID: <68d9921e.a70a0220.10c4b.0025.GAE@google.com> (raw)
In-Reply-To: <87ecrq2xr2.fsf@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
./include/linux/thread_info.h:244:4: error: call to '__bad_copy_from' declared with 'error' attribute: copy source size is too small
drivers/nvme/target/fc.c:150:2: warning: 'counted_by' should not be applied to an array with element of unknown size because 'struct nvmet_fc_fcp_iod' is a struct type with a flexible array member. This will be an error in a future compiler version [-Wbounds-safety-counted-by-elt-type-unknown-size]
Tested on:
commit: 6f861765 fs: Block writes to mounted block devices
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=fc26c366038b54261e53
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
next parent reply other threads:[~2025-09-28 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ecrq2xr2.fsf@gmail.com>
2025-09-28 19:53 ` syzbot [this message]
[not found] <87a52e2uxz.fsf@gmail.com>
2025-09-28 20:43 ` [syzbot] [fs?] UBSAN: shift-out-of-bounds in befs_check_sb syzbot
2023-07-12 13:47 syzbot
2024-03-03 8:30 ` 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=68d9921e.a70a0220.10c4b.0025.GAE@google.com \
--to=syzbot+fc26c366038b54261e53@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xandfury@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