All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+4687ab80180e5d724f51@syzkaller.appspotmail.com>
To: andi.shyti@kernel.org, gregkh@linuxfoundation.org,
	 linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 wsa+renesas@sang-engineering.com
Subject: Re: [syzbot] [usb?] WARNING in osif_xfer/usb_submit_urb
Date: Thu, 24 Jul 2025 07:37:02 -0700	[thread overview]
Message-ID: <6882450e.a00a0220.2f88df.002a.GAE@google.com> (raw)
In-Reply-To: <681853be.a70a0220.254cdc.0045.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 56ad91c1aa9c18064348edf69308080b03c9dc48
Author: Wolfram Sang <wsa+renesas@sang-engineering.com>
Date:   Thu May 22 06:42:35 2025 +0000

    i2c: robotfuzz-osif: disable zero-length read messages

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15b114f0580000
start commit:   4f79eaa2ceac kbuild: Properly disable -Wunterminated-strin..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=a9a25b7a36123454
dashboard link: https://syzkaller.appspot.com/bug?extid=4687ab80180e5d724f51
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=103081cc580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17ba139b980000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: i2c: robotfuzz-osif: disable zero-length read messages

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2025-07-24 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05  5:59 [syzbot] [usb?] WARNING in osif_xfer/usb_submit_urb syzbot
2025-07-24 14:37 ` syzbot [this message]
2025-07-24 15:26   ` Wolfram Sang

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=6882450e.a00a0220.2f88df.002a.GAE@google.com \
    --to=syzbot+4687ab80180e5d724f51@syzkaller.appspotmail.com \
    --cc=andi.shyti@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=wsa+renesas@sang-engineering.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.