[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170929225949.GP8463@localhost.localdomain>
Date: Fri, 29 Sep 2017 16:59:49 -0600
From: Keith Busch <keith.busch@...el.com>
To: Martin Wilck <mwilck@...e.com>
Cc: Jens Axboe <axboe@...nel.dk>, Christoph Hellwig <hch@....de>,
Johannes Thumshirn <jthumshirn@...e.de>,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
Hannes Reinecke <hare@...e.de>, linux-nvme@...ts.infradead.org,
Martin Wilck <mwilck@...e.de>
Subject: Re: [PATCH 1/2] block: genhd: add device_add_disk_with_groups
On Thu, Sep 28, 2017 at 09:36:36PM +0200, Martin Wilck wrote:
> In the NVME subsystem, we're seeing a race condition with udev where
> device_add_disk() is called (which triggers an "add" uevent), and a
> sysfs attribute group is added to the disk device afterwards.
> If udev rules access these attributes before they are created,
> udev processing of the device is incomplete, in particular, device
> WWIDs may not be determined correctly.
>
> To fix this, this patch introduces a new function
> device_add_disk_with_groups(), which takes a list of attribute groups
> and adds them to the device before sending out uevents.
>
> Signed-off-by: Martin Wilck <mwilck@...e.com>
Is NVMe the only one having this problem? Was putting our attributes in
the disk's kobj a bad choice?
Any, looks fine to me.
Reviewed-by: Keith Busch <keith.busch@...el.com>
Powered by blists - more mailing lists