From: sashiko-bot@kernel.org
To: "Pengfei Lv" <lvpengfei20@huawei.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v3] usb: core: hub: Re-guess ep0 maxpacket size after reset
Date: Mon, 09 Nov 2026 09:54:42 +0000 [thread overview]
Message-ID: <sashiko-outbox-204761@kernel.org> (raw)
In-Reply-To: <20261109093935.2634235-1-lvpengfei20@huawei.com>
> Per USB 2.0 spec section 5.5.3, the ep0 maxpacket size is fixed for
> all device speeds except full-speed devices, where it can be 8, 16,
> 32, or 64 bytes and can only be determined by reading the device
> descriptor. During initial enumeration the USB core guesses 64 bytes
> for full-speed devices; after reading the descriptor, the real value
> is stored in udev->ep0.desc.wMaxPacketSize and applied to hardware by
> usb_ep0_reinit().
>
> Commit ff33299ec8bb ("USB: core: Fix race by not overwriting
> udev->descriptor in hub_port_init()") guarded the ep0 maxpacket guess
> block with "if (initial)", so on the reset path the guess is skipped
> and the host keeps using the value from the previous enumeration. If
> a buggy full-speed device responds with one 8-byte packet and NAKs
> all further polling, the HC doesn't recognize a short transfer but
> keeps polling for the rest of the descriptor till unlink, and the
> [ ... ]
> data stage.
>
> Fixes: ff33299ec8bb ("USB: core: Fix race by not overwriting udev->descriptor in hub_port_init()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Pengfei Lv <lvpengfei20@huawei.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109093935.2634235-1-lvpengfei20@huawei.com?part=1
next prev parent reply other threads:[~2026-11-09 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 12:44 [PATCH] usb: core: hub: Re-guess ep0 maxpacket size on reset Pengfei Lv
2026-11-04 12:57 ` sashiko-bot
2026-11-04 14:59 ` Alan Stern
2026-11-04 17:36 ` Michal Pecio
2026-11-05 5:06 ` Alan Stern
2026-11-05 12:30 ` Michal Pecio
2026-11-05 8:41 ` Pengfei Lv
2026-11-05 15:46 ` Alan Stern
2026-11-06 3:16 ` [PATCH v2] " Pengfei Lv
2026-11-06 3:34 ` sashiko-bot
2026-11-06 22:01 ` Michal Pecio
2026-11-06 7:17 ` Michal Pecio
2026-11-09 9:39 ` [PATCH v3] usb: core: hub: Re-guess ep0 maxpacket size after reset Pengfei Lv
2026-11-09 9:54 ` sashiko-bot [this message]
2026-11-09 16:05 ` Alan Stern
2026-11-09 20:34 ` Michal Pecio
2026-11-10 3:00 ` Alan Stern
2026-11-10 3:30 ` [PATCH v4] " Pengfei Lv
2026-11-10 3:52 ` sashiko-bot
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=sashiko-outbox-204761@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lvpengfei20@huawei.com \
--cc=sashiko-reviews@lists.linux.dev \
/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