All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ce77725b89b7bd52425c@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, stern@rowland.harvard.edu,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in usbtmc_ioctl/usb_submit_urb (2)
Date: Mon, 01 May 2023 08:42:57 -0700	[thread overview]
Message-ID: <0000000000004b903305faa3ad0c@google.com> (raw)
In-Reply-To: <38c0a2fd-cd9c-43b3-99f0-4f9ed2fdc69f@rowland.harvard.edu>

Hello,

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

Reported-and-tested-by: syzbot+ce77725b89b7bd52425c@syzkaller.appspotmail.com

Tested on:

commit:         58390c8c Merge tag 'iommu-updates-v6.4' of git://git.k..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
console output: https://syzkaller.appspot.com/x/log.txt?x=12708e68280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d56ffc213bf6bf4a
dashboard link: https://syzkaller.appspot.com/bug?extid=ce77725b89b7bd52425c
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11ff68e8280000

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

  reply	other threads:[~2023-05-01 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 10:16 [syzbot] [usb?] WARNING in usbtmc_ioctl/usb_submit_urb (2) syzbot
2023-05-01 11:59 ` syzbot
2023-05-01 15:19   ` Alan Stern
2023-05-01 15:42     ` syzbot [this message]
2023-05-01 18:22       ` [PATCH] USB: usbtmc: Fix direction for 0-length ioctl control messages Alan Stern
2023-05-02 22:35 ` [syzbot] [usb?] WARNING in usbtmc_ioctl/usb_submit_urb (2) 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=0000000000004b903305faa3ad0c@google.com \
    --to=syzbot+ce77725b89b7bd52425c@syzkaller.appspotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --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 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.