All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: CO <co@bugs.sh>
Cc: linux-usb@vger.kernel.org
Subject: Re: [BUG] drivers/usb: out-of-bounds in xhci_queue_bulk_tx()
Date: Tue, 1 Sep 2026 15:39:28 +0200	[thread overview]
Message-ID: <2026090139-shortlist-junkie-9bee@gregkh> (raw)
In-Reply-To: <010001a05cec684a-64e27a6c-d9bf-4b18-8fd7-19fd00c3f42e-000000@email.amazonses.com>

On Tue, Sep 01, 2026 at 12:23:12PM +0000, CO wrote:
> Is it acceptable to send bug reports (without a patch, such as this
> bug report) to the list like syzbot?

I can't tell anyone what to do, but if you have found a bug, it's
usually best to submit a patch to fix it, as you have a reproducer so
you can test it better than anyone, right?

> As you mentioned, we understand many of them will be ignored since
> reviewers would prioritize patches. But we'll work with community
> contributors who would like to work to write a patch for them. (which
> faster than just two of us)

These days you can feed a bug report into a local LLM and get out a
first-cut of a patch quite easily.

But sure, posting bug reports is fine, but again, patches are better :)

thanks,

greg k-h

  reply	other threads:[~2026-09-01 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 12:43 [BUG] drivers/usb: out-of-bounds in xhci_queue_bulk_tx() co
2026-08-27 12:50 ` Greg Kroah-Hartman
2026-08-27 17:31   ` Xiang Mei
2026-08-28  2:00     ` CO
2026-08-28  5:36       ` Greg KH
2026-08-29  6:07         ` CO
2026-08-29  6:18           ` Greg KH
2026-08-29  6:42             ` Cedalion
2026-08-29  6:59               ` Greg KH
2026-08-29  7:34                 ` CO
2026-08-29  7:54                   ` Greg KH
2026-09-01 12:23                     ` CO
2026-09-01 13:39                       ` Greg KH [this message]
2026-08-27 22:47 ` Michal Pecio
2026-09-02 11:24   ` [PATCH] usb: xhci: Fix bounce buffer overflow Michal Pecio
2026-09-02 13:39     ` Mathias Nyman

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=2026090139-shortlist-junkie-9bee@gregkh \
    --to=greg@kroah.com \
    --cc=co@bugs.sh \
    --cc=linux-usb@vger.kernel.org \
    /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.