All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: mruijter@primelogic.nl, hch@lst.de,
	linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [PATCH 1/3] nvmet: allow user to set the ns readonly
Date: Thu, 1 Oct 2020 19:24:29 +0200	[thread overview]
Message-ID: <20201001172429.GA29997@lst.de> (raw)
In-Reply-To: <20201001024427.40753-2-chaitanya.kulkarni@wdc.com>

On Wed, Sep 30, 2020 at 07:44:25PM -0700, Chaitanya Kulkarni wrote:
> From: "Mark Ruijter" <mruijter@primelogic.nl>
> 
> User may want to export readonly ns to host in order to export
> read-only snapshots. Right now we don't have configfs attribute to
> allow user to mark readonly & export ns.
> 
> Add a configfs attribute such that user can set the ns and export ns
> readonly when it is not enabled.

I thin kwe also need to expose this as permantently write protected
throught the write protection feature on the get side, and ensure
a set features can't change the setting.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-10-01 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  2:44 [PATCH 0/3] nvmet: allow target to export readonly ns Chaitanya Kulkarni
2020-10-01  2:44 ` [PATCH 1/3] nvmet: allow user to set the ns readonly Chaitanya Kulkarni
2020-10-01 17:24   ` Christoph Hellwig [this message]
2020-10-01  2:44 ` [PATCH 2/3] nvmet: allow readonly bdev-ns to be configured Chaitanya Kulkarni
2020-10-01  2:44 ` [PATCH 3/3] nvmet: allow readonly file-ns " Chaitanya Kulkarni

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=20201001172429.GA29997@lst.de \
    --to=hch@lst.de \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mruijter@primelogic.nl \
    --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 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.