From: syzbot <syzbot+30c83da54e948f6e9436@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
yuichtsu@amazon.com
Subject: Re: [syzbot] [v9fs?] UBSAN: shift-out-of-bounds in v9fs_get_tree
Date: Fri, 22 Aug 2025 07:56:02 -0700 [thread overview]
Message-ID: <68a88502.a00a0220.33401d.025a.GAE@google.com> (raw)
In-Reply-To: <20250822133148.199-1-yuichtsu@amazon.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/9p/vfs_super.c
patch: **** unexpected end of file in patch
Tested on:
commit: 0f4c93f7 Add linux-next specific files for 20250822
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=6d1acc6b9e1fca1b
dashboard link: https://syzkaller.appspot.com/bug?extid=30c83da54e948f6e9436
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=15230062580000
next prev parent reply other threads:[~2025-08-22 14:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 2:58 [syzbot] [v9fs?] UBSAN: shift-out-of-bounds in v9fs_get_tree syzbot
2025-08-21 3:48 ` Dominique Martinet
2025-08-21 4:06 ` syzbot
2025-09-24 23:14 ` Eric Sandeen
2025-08-21 8:47 ` Hillf Danton
2025-08-21 9:23 ` syzbot
2025-08-22 13:31 ` Yuichiro Tsuji
2025-08-22 14:56 ` syzbot [this message]
2025-08-22 13:45 ` Yuichiro Tsuji
2025-08-22 17:47 ` syzbot
2025-08-22 14:27 ` Edward Adam Davis
2025-08-22 18:05 ` syzbot
2025-08-22 14:41 ` [PATCH next] 9p: Correct the session info Edward Adam Davis
2025-08-22 23:22 ` [PATCH next V2] " Edward Adam Davis
2025-08-23 6:34 ` Dominique Martinet
2025-09-24 22:19 ` Eric Sandeen
2025-09-25 2:17 ` Dominique Martinet
2025-09-25 4:29 ` Eric Sandeen
2025-09-25 7:24 ` Dominique Martinet
2025-09-28 4:00 ` Forwarded: Re: [syzbot] [v9fs?] UBSAN: shift-out-of-bounds in v9fs_get_tree syzbot
2025-09-28 19:04 ` syzbot
[not found] <87ikh32pm3.fsf@gmail.com>
2025-09-28 4:45 ` syzbot
[not found] <87h5wm2ybu.fsf@gmail.com>
2025-09-28 20:44 ` 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=68a88502.a00a0220.33401d.025a.GAE@google.com \
--to=syzbot+30c83da54e948f6e9436@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yuichtsu@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.