Netdev List
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Ömer Mete Kaya" <omermetekaya0@gmail.com>,
	oneukum@suse.com, netdev@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	david.laight.linux@gmail.com,
	syzbot+04cd90bb99c6ef81a65d@syzkaller.appspotmail.com
Subject: Re: [PATCH net v6] usbnet: fix smp_processor_id() use in preemptible context
Date: Wed, 14 Oct 2026 21:11:41 +0200	[thread overview]
Message-ID: <20261014191141.GxlJhR1e@linutronix.de> (raw)
In-Reply-To: <41af30de-4725-4913-9ad8-54d1dea2d4b8@rowland.harvard.edu>

On 2026-10-12 22:09:25 [-0400], Alan Stern wrote:
> > > Today you fix VHCI, tomorrow some other virtual HCD will cause problems.
> > 
> > We don't have other virtual HCDs, do we?
> 
> Well, we've got dummy-hcd.  And just recently there was an RFC post with 
> a virtio USB HCD implementation.  It wouldn't be surprising to encounter 
> other ones.

dummy-hcd is timer driven (so BH). Without looking at virtio I would
expect it to be interrupt driven.

> Also, don't forget, URBs can complete in several different ways.  
> There's normal completion, explicit unlinking, unlinking because the 
> device was unplugged, unlinking because the device or HC is going into 
> suspend, and so on.  And there's a difference between URBs sent to 
> root hubs as opposed to devices actually on the bus.  Not to mention 
> that in some cases completions may occur synchronously with submission 
> or unlinking, even though they usually are asynchronous.

True.

> > Do you want to document it yourself and have me do the VHCI bits?
> 
> At the moment, the only thing I think we can actually guarantee is that 
> completion handlers will be called with local interrupts disabled.  No 
> commitments about process context vs. interrupt context vs. BH context 
> or anything else.

"local interrupts disabled" as is local_irq_disable()? If so, that is
not the case. If it completes in BH context (due to HCD_BH) then
interrupts remain enabled.

> Of course, in special cases you might know more about how a particular 
> HCD works.  But except for platform-specific settings, it's hard to be 
> certain that your driver will always be used with that one particular 
> HCD.
> 
> If this is okay with you, I can write a documentation patch.

Sure. The kernel doc for usb_hcd_giveback_urb() says BH or caller's
context. I think you need to clarify that part and once we have tha, we
can proceed with the drivers.

Thank you.

> Alan Stern

Sebastian

  parent reply	other threads:[~2026-10-14 19:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 21:59 [PATCH net v6] usbnet: fix smp_processor_id() use in preemptible context Ömer Mete Kaya
2026-10-08  3:00 ` Jakub Kicinski
2026-10-08 14:16   ` Alan Stern
2026-10-08 16:43     ` Jakub Kicinski
2026-10-08 18:03       ` Alan Stern
2026-10-09 11:31         ` Greg Kroah-Hartman
2026-10-12 19:49           ` Sebastian Andrzej Siewior
2026-10-12 20:26             ` Alan Stern
2026-10-12 21:25               ` Sebastian Andrzej Siewior
2026-10-13  2:09                 ` Alan Stern
2026-10-13  9:11                   ` Paolo Abeni
2026-10-13  9:22                     ` Sebastian Andrzej Siewior
2026-10-14 19:11                   ` Sebastian Andrzej Siewior [this message]
2026-10-14 19:22                     ` Alan Stern
2026-10-14 22:04                       ` Sebastian Andrzej Siewior
2026-10-13  8:54               ` Oliver Neukum
2026-10-13  9:20                 ` Sebastian Andrzej Siewior

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=20261014191141.GxlJhR1e@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=david.laight.linux@gmail.com \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=omermetekaya0@gmail.com \
    --cc=oneukum@suse.com \
    --cc=pabeni@redhat.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzbot+04cd90bb99c6ef81a65d@syzkaller.appspotmail.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