All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b73659f5bb96fac34820@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, jeremy.linton@arm.com,
	 linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	 stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
	 usama.anjum@collabora.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [usb?] INFO: task hung in usbdev_open (2)
Date: Wed, 18 Oct 2023 03:30:34 -0700	[thread overview]
Message-ID: <0000000000002af93d0607fb2163@google.com> (raw)
In-Reply-To: <dc016529-51f7-4a8a-8c67-54a15b19b78b@collabora.com>

Hello,

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

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

Tested on:

commit:         2dac7569 Add linux-next specific files for 20231018
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git next-20231018
console output: https://syzkaller.appspot.com/x/log.txt?x=161f5833680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b9f4d682cd6282b3
dashboard link: https://syzkaller.appspot.com/bug?extid=b73659f5bb96fac34820
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2023-10-18 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 11:48 INFO: task hung in usbdev_open (2) syzbot
2023-04-01  6:15 ` [syzbot] [usb?] " syzbot
2023-10-18  9:46   ` Muhammad Usama Anjum
2023-10-18 10:30     ` syzbot [this message]

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=0000000000002af93d0607fb2163@google.com \
    --to=syzbot+b73659f5bb96fac34820@syzkaller.appspotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.linton@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=usama.anjum@collabora.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.