public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+78cae3f37c62ad092caa@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 viswanathiyyappan@gmail.com
Subject: Re: [syzbot] [net?] [usb?] WARNING in rtl8150_start_xmit/usb_submit_urb
Date: Fri, 19 Sep 2025 11:45:02 -0700	[thread overview]
Message-ID: <68cda4ae.a00a0220.37dadf.001e.GAE@google.com> (raw)
In-Reply-To: <CAPrAcgNhZmR4Z323aHXC-Vfwk8LBHFe9=mtR-CKQ3iADO5uoJg@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+78cae3f37c62ad092caa@syzkaller.appspotmail.com
Tested-by: syzbot+78cae3f37c62ad092caa@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=16361858580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=135377594f35b576
dashboard link: https://syzkaller.appspot.com/bug?extid=78cae3f37c62ad092caa
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=133320e2580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2025-09-19 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPrAcgNhZmR4Z323aHXC-Vfwk8LBHFe9=mtR-CKQ3iADO5uoJg@mail.gmail.com>
2025-09-19 18:45 ` syzbot [this message]
     [not found] <CAPrAcgNtStXdajzsDgWqyLVAMok5gpKtmt=zU2vWNr93hhzGPg@mail.gmail.com>
2025-09-17 10:26 ` [syzbot] [net?] [usb?] WARNING in rtl8150_start_xmit/usb_submit_urb syzbot
     [not found] <CAPrAcgP7f7rGNKKvHYe72jHMjo2D_8wRzoPt61stAiM0fccOhg@mail.gmail.com>
2025-09-15 17:52 ` syzbot
     [not found] <CAPrAcgMXXKyOCec=SXF6_MD4csgODiO41d0hQ_KsBsRmzoxk+w@mail.gmail.com>
2025-09-12  8:32 ` syzbot
2025-08-29 18:38 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=68cda4ae.a00a0220.37dadf.001e.GAE@google.com \
    --to=syzbot+78cae3f37c62ad092caa@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viswanathiyyappan@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