From: syzbot <syzbot+d8fd35fa6177afa8c92b@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, apopple@nvidia.com, byungchul@sk.com,
david@redhat.com, gourry@gourry.net, joshua.hahnjy@gmail.com,
krishnagopi487@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, matthew.brost@intel.com, rakie.kim@sk.com,
syzkaller-bugs@googlegroups.com, ying.huang@linux.alibaba.com,
ziy@nvidia.com
Subject: Re: [syzbot] [mm?] WARNING in raw_ioctl
Date: Sat, 25 Oct 2025 06:15:02 -0700 [thread overview]
Message-ID: <68fccd56.a00a0220.1c5a1.0002.GAE@google.com> (raw)
In-Reply-To: <y6cshcj5anakdq2l3yq43febnftvttwjvoeounl6pincoayhfc@fjiiuk6ah4tt>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file drivers/usb/gadget/legacy/raw_gadget.c
checking file include/uapi/linux/usb/raw_gadget.h
patch: **** unexpected end of file in patch
Tested on:
commit: 72fb0170 Add linux-next specific files for 20251024
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=e812d103f45aa955
dashboard link: https://syzkaller.appspot.com/bug?extid=d8fd35fa6177afa8c92b
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=16ea4be2580000
next prev parent reply other threads:[~2025-10-25 13:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 23:11 [syzbot] [mm?] WARNING in raw_ioctl syzbot
2025-10-25 9:16 ` Gopi Krishna Menon
2025-10-25 10:25 ` syzbot
2025-10-25 13:02 ` Gopi Krishna Menon
2025-10-25 13:15 ` syzbot [this message]
2025-10-25 13:20 ` Gopi Krishna Menon
2025-10-25 13:29 ` syzbot
2025-10-25 13:34 ` Gopi Krishna Menon
2025-10-25 13:58 ` syzbot
2025-10-25 15:52 ` Gopi Krishna Menon
2025-10-25 16:43 ` syzbot
2025-10-28 16:27 ` Gopi Krishna Menon
2025-10-28 16:56 ` 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=68fccd56.a00a0220.1c5a1.0002.GAE@google.com \
--to=syzbot+d8fd35fa6177afa8c92b@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=krishnagopi487@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=rakie.kim@sk.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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.