From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 3/3] nvme: make SG_IO support optional
Date: Thu, 24 Dec 2015 16:45:12 +0100 [thread overview]
Message-ID: <20151224154512.GA22789@lst.de> (raw)
In-Reply-To: <20151224152945.GA7262@localhost.localdomain>
On Thu, Dec 24, 2015@03:29:46PM +0000, Keith Busch wrote:
> On Thu, Dec 24, 2015@12:40:40PM +0100, Christoph Hellwig wrote:
> > On Thu, Dec 24, 2015@01:31:32PM +0200, Sagi Grimberg wrote:
> > > OK, I see what you mean. We can look at having multipathd ioctl'ing
> > > identify_ns at some point...
> >
> > block/for-next has the nguid available as a sysfs attribute, that's
> > all we should need.
>
> Off the top of your head, do you happen to know how to point multipathd
> to the new attribute? Is this a code change or just a configuration rule?
With the most recent mutlipath-tools there should be no need to patch
mutipath-tools. Just make sure udev sets the ID_SERIAL attribute
correctly, which I think some folks were already looking into. An
explicit getuid callout that just reads the file should also work
with any versions, although the most recent ones call it deprectated.
prev parent reply other threads:[~2015-12-24 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 10:15 namespace list locking and ioctl fixes Christoph Hellwig
2015-12-24 10:15 ` [PATCH 1/3] nvme: synchronize access to ctrl->namespaces Christoph Hellwig
2015-12-24 10:36 ` Sagi Grimberg
2015-12-24 11:08 ` Christoph Hellwig
2015-12-24 10:15 ` [PATCH 2/3] nvme: fixes for NVME_IOCTL_IO_CMD on the char device Christoph Hellwig
2015-12-24 10:37 ` Sagi Grimberg
2015-12-24 10:15 ` [PATCH 3/3] nvme: make SG_IO support optional Christoph Hellwig
2015-12-24 10:39 ` Sagi Grimberg
2015-12-24 11:12 ` Christoph Hellwig
2015-12-24 11:31 ` Sagi Grimberg
2015-12-24 11:40 ` Christoph Hellwig
2015-12-24 15:29 ` Keith Busch
2015-12-24 15:45 ` Christoph Hellwig [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=20151224154512.GA22789@lst.de \
--to=hch@lst.de \
/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;
as well as URLs for NNTP newsgroup(s).