public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, Wendy Wang <wendy.wang@intel.com>
Subject: Re: [PATCH 1/1] xhci: Fix null pointer dereference during S4 resume when resetting ep0
Date: Mon, 18 Dec 2023 11:29:53 +0200	[thread overview]
Message-ID: <865a55f7-bf0d-692a-0187-8fe4c6dabd38@linux.intel.com> (raw)
In-Reply-To: <2023121515-paper-annuity-a0e3@gregkh>

On 15.12.2023 19.27, Greg KH wrote:
> On Fri, Dec 15, 2023 at 02:57:07PM +0200, Mathias Nyman wrote:
>> During device enumeration usb core resets endpoint 0 if the max packet
>> size value differs from the one read from the device descriptor.
>>
>> usb core will additionally reset endpoint 0 during S4 resume, before
>> re-enumerating the device, if the device has a reset-resume flag set.
>>
>> In this case the xhci device representation vdev may be lost due to
>> xHC restore error and re-initialization during S4 resume.
>>
>> Make sure slot_id and vdev are valid before trying to re-configure max
>> packet size during endpoint 0 reset.
>> max packet size will be re-configured later during re-enumeration.
>>
>> This fixes commit e34900f46cd6 ("xhci: Reconfigure endpoint 0 max packet
>> size only during endpoint reset") which is currently in usb-next,
>> on its way to 6.7
> 
> You mean "6.8" here, right?

Ah, yes it should be 6.8, my mistake.

Thanks
Mathias



      reply	other threads:[~2023-12-18  9:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 12:57 [PATCH 0/1] xhci feature-fix for usb-next Mathias Nyman
2023-12-15 12:57 ` [PATCH 1/1] xhci: Fix null pointer dereference during S4 resume when resetting ep0 Mathias Nyman
2023-12-15 17:27   ` Greg KH
2023-12-18  9:29     ` Mathias Nyman [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=865a55f7-bf0d-692a-0187-8fe4c6dabd38@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=wendy.wang@intel.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