All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220033] xhci: Compliance Issue - avg_trb_len not set for EP0 during Address Device Command
Date: Wed, 07 May 2025 19:58:02 +0000	[thread overview]
Message-ID: <bug-220033-208809-TAs7aHTser@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220033-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220033

Michał Pecio (michal.pecio@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.pecio@gmail.com

--- Comment #3 from Michał Pecio (michal.pecio@gmail.com) ---
(In reply to Chen-Tzu-Chieh from comment #0)
> Some xHCI hardware vendors may validate the Input Context at Address Device
> time and reject contexts with invalid values, potentially causing device
> enumeration issues.
A scarier (and more likely?) possibility is HCs failing to validate this field
and yet assuming that it's non-zero, then dividing by zero or doing some other
stupid thing and crashing and burning. Bonus if it only happens once in a blue
moon.

But as Mathias found, the spec is self-contradictory, so it works both ways...

> While xhci_endpoint_init() later sets avg_trb_len correctly,
Are you sure? ;)

This function is only called from add_endpoint(), which doesn't seem to ever be
called on EP 0. But non-default control endpoints would be set to 8 indeed.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-05-07 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 13:31 [Bug 220033] New: xhci: Compliance Issue - avg_trb_len not set for EP0 during Address Device Command bugzilla-daemon
2025-05-06 14:37 ` [Bug 220033] " bugzilla-daemon
2025-05-07 10:21 ` bugzilla-daemon
2025-05-07 19:58 ` bugzilla-daemon [this message]
2025-05-13  9:17 ` bugzilla-daemon

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=bug-220033-208809-TAs7aHTser@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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.