From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@fb.com>,
"Sagi Grimberg" <sagi@grimberg.me>,
linux-nvme@lists.infradead.org,
"Javier González" <javier.gonz@samsung.com>
Subject: Re: [PATCH] nvme: introduce passthrough ioctl for multipath
Date: Sat, 20 Feb 2021 06:26:37 +0900 [thread overview]
Message-ID: <20210219212637.GA175471@localhost.localdomain> (raw)
In-Reply-To: <20210218084014.GA17997@lst.de>
On 21-02-18 09:40:14, Christoph Hellwig wrote:
> On Wed, Feb 17, 2021 at 11:14:55AM +0900, Minwoo Im wrote:
> > > A container could read data from namespaces assigned to a different
> > > container.
> >
> > Now I got your point! Thanks Keith, please ignore this patch :)
>
> Note that Javier has been working on exposing access to namespaces
> with unsupported command sets for ioctls. If that is what you are
> looking for.
Thank you for the information!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-02-19 21:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 11:01 [PATCH 0/2] nvme: support I/O passthrough for multipath Minwoo Im
2021-02-14 11:01 ` [PATCH] nvme: introduce passthrough ioctl " Minwoo Im
2021-02-15 17:02 ` Keith Busch
2021-02-16 9:51 ` Minwoo Im
2021-02-16 17:57 ` Keith Busch
2021-02-17 2:14 ` Minwoo Im
2021-02-18 8:40 ` Christoph Hellwig
2021-02-18 8:48 ` Javier González
2021-02-19 21:27 ` Minwoo Im
2021-02-19 21:26 ` Minwoo Im [this message]
2021-02-14 11:01 ` [nvme-cli PATCH] nvme: add [--mpath|-M] option to io-passthru Minwoo Im
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=20210219212637.GA175471@localhost.localdomain \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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