From mboxrd@z Thu Jan 1 00:00:00 1970 From: hch@lst.de (Christoph Hellwig) Date: Wed, 4 Oct 2017 08:15:33 +0200 Subject: [PATCH 3/6] nvme: claim block devices In-Reply-To: References: <1506952559-1588-1-git-send-email-hare@suse.de> <1506952559-1588-4-git-send-email-hare@suse.de> <20171002164218.GA11886@lst.de> <20171003115506.GC24650@lst.de> Message-ID: <20171004061533.GA20131@lst.de> On Wed, Oct 04, 2017@07:42:00AM +0200, Hannes Reinecke wrote: > Hmm. Not sure how you would be doing that. Who should be doing the > claiming? Typically the claim is done whenever a device is created on > top of the other... We'd need a callback in the driver if it is claimed, and use that to for propagating the claim, or use a shared struture to record the claim. I haven't looked into the details yet, though. > What about an alternative plan: make creation of the subsystem device > fully dynamic. > But if a subsystem device is created it will always claim the underlying > device. Then we can make the creation dependent on the NMIC attribute, > and existing setups would not be affected. This doesn't work because a lot of devices can just set NMIC. E.g. every namespace exported by the Linux NVMe target.