From: syzbot <syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4)
Date: Fri, 19 Sep 2025 21:48:03 -0700 [thread overview]
Message-ID: <68ce3203.050a0220.13cd81.0010.GAE@google.com> (raw)
In-Reply-To: <20250920025550.7294-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
Tested-by: syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com
Tested on:
commit: 846bd222 Add linux-next specific files for 20250919
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=162b5c7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=135377594f35b576
dashboard link: https://syzkaller.appspot.com/bug?extid=5a2250fd91b28106c37b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=16eabe42580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-09-20 4:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 21:55 [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
2025-09-19 16:04 ` Forwarded: test linux-next 7fa4d8dc380f syzbot
2025-09-20 0:43 ` [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) Hillf Danton
2025-09-20 1:15 ` syzbot
2025-09-20 2:55 ` Hillf Danton
2025-09-20 4:48 ` syzbot [this message]
2025-09-20 10:59 ` Forwarded: syz test syzbot
2025-09-20 18:55 ` Forwarded: re-test syzbot
[not found] <CAL4kbRPgrQO_QYOGBFGoPEG9OZet-LVSvGDT2+37-uiKRWh0ng@mail.gmail.com>
2025-09-19 17:28 ` [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
[not found] <CAL4kbRMa8snwYuwi4zNjx9bNbrRg=MN+xkadQ=89Dc6URRCOog@mail.gmail.com>
2025-09-20 11:37 ` syzbot
[not found] <CAL4kbRPcgyZtXEGuiAR+dpiqfsawnwyKovtKy_vWEgowF+HDMQ@mail.gmail.com>
2025-09-20 20:09 ` 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=68ce3203.050a0220.13cd81.0010.GAE@google.com \
--to=syzbot+5a2250fd91b28106c37b@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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