[PATCH V4 3/9] nvme: fix race condition between connected uevent and STARTED_ONCE flag

[Keith Busch]

On Mon, May 11, 2026 at 05:45:36PM +0200, Maurizio Lombardi wrote:
> On Mon May 11, 2026 at 5:09 PM CEST, Keith Busch wrote:
> > On Mon, May 11, 2026 at 03:54:04PM +0300, Sagi Grimberg wrote:
> >> 
> >> > On Mon, May 11, 2026 at 01:10:34AM +0300, Sagi Grimberg wrote:
> >> > > This should even go as a separate patch:
> >> > You mean a stadalone fix?  Because it already is a separate patch.
> >> 
> >> Yes, this is a race condition fix that can go separately.
> >
> > Sure thing, I've applied patch 3/9 to nvme-7.1 as a separate bug fix.
> 
> Oh, that was way faster than I expected.
> 
> The issue is that, in explaining the rationale behind PATCH 3, I
> mentioned in its commit message the admin_timeout sysfs attribute
> introduced by this patchset.
> 
> You may want to remove that reference if you plan to merge patch 3
> indipendently of the rest of this patchset.
> 
> In the vanilla kernel, the only sysfs attribute that could be affected by
> this race condition is nvme_sysfs_delete().

Ah, thanks. I got to this one quicker because I had some free time for
patch maintenance. I'll fix up the message.