All of lore.kernel.org
 help / color / mirror / Atom feed
From: mwilck@suse.com (Martin Wilck)
Subject: [PATCH] nvme: register ns_id attributes as default sysfs groups
Date: Fri, 20 Jul 2018 16:50:06 +0200	[thread overview]
Message-ID: <2000865cfb5da244b9e5e3e3405c3db6d133e63a.camel@suse.com> (raw)
In-Reply-To: <b7314028-d878-a667-968f-fcabf30f65fd@suse.de>

On Tue, 2018-07-17@15:20 +0200, Hannes Reinecke wrote:
> On 07/17/2018 03:12 PM, Christoph Hellwig wrote:
> > On Mon, Jul 16, 2018@12:37:21PM +0200, Hannes Reinecke wrote:
> > > We should be registering the ns_id attributes as default sysfs
> > > groups,
> > > otherwise we have a race condition between nvme_mpath_add_disk()
> > > and
> > > nvme_mpath_remove_disk() which will lead to a kobject warning
> > > during
> > > rapid connect/disconnect cycles.
> > > 
> > > Reported-by: James Smart <james.smart at broadcom.com>
> > > Signed-off-by: Hannes Reinecke <hare at suse.com>
> > > ---
> > 
> > Didn't Martin Wilck habe a patch to pass the default attribute
> > group to an add_disk variant?  We've been waiting for him to just
> > clean it up a bit, and it would be a lot less ugly than opencoding
> > the device model details in the callers.
> > 
> 
> Since you mention it, indeed, there was something.
> I'll see to resurrect his patches.
> 
> Or poke him directly...

Right, it has been on my list for some time, didn't get down to it.
I'll see what I can do next week.

Martin

-- 
Dr. Martin Wilck <mwilck at suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

      reply	other threads:[~2018-07-20 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 10:37 [PATCH] nvme: register ns_id attributes as default sysfs groups Hannes Reinecke
2018-07-16 11:00 ` Sagi Grimberg
2018-07-17 13:12 ` Christoph Hellwig
2018-07-17 13:20   ` Hannes Reinecke
2018-07-20 14:50     ` Martin Wilck [this message]

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=2000865cfb5da244b9e5e3e3405c3db6d133e63a.camel@suse.com \
    --to=mwilck@suse.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 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.