From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Cheng Yongkang <teel4res@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] usb: core: resume clears needs_altsetting0 even on failure
Date: Mon, 16 Nov 2026 10:33:25 +0100 [thread overview]
Message-ID: <2026111636-snowless-pacify-e2f6@gregkh> (raw)
In-Reply-To: <20261115163654.226373-1-teel4res@gmail.com>
On Sun, Nov 15, 2026 at 08:36:54AM -0800, Cheng Yongkang wrote:
> Hi Greg, Alan,
>
> I hit a corner case in usb_resume_interface(). It needs a device that
> fails SET_INTERFACE(0) both when the driver is unbound and again at
> resume, so it may not be worth fixing.
<snip>
As your "tool" found these, it can also make a proposed patch and test
it for them as well. Please do so, don't just send "empty" messages
that claim a problem is found by a static analysis program.
thanks,
greg k-h
prev parent reply other threads:[~2026-11-16 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 16:36 [BUG] usb: core: resume clears needs_altsetting0 even on failure Cheng Yongkang
2026-11-16 9:33 ` Greg Kroah-Hartman [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=2026111636-snowless-pacify-e2f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=teel4res@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