linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] nvdimm: preserve read-only setting for pmem devices
@ 2018-05-31 23:36 Robert Elliott
  2018-06-01  4:16 ` Dan Williams
  0 siblings, 1 reply; 2+ messages in thread
From: Robert Elliott @ 2018-05-31 23:36 UTC (permalink / raw)
  To: linux-nvdimm

The pmem driver don't honor a forced read-only setting for very long:
	$ blockdev --setro /dev/pmem0
	$ blockdev --getro /dev/pmem0
	1

followed by various commands like these:
	$ blockdev --rereadpt /dev/pmem0
	or
	$ mkfs.ext4 /dev/pmem0

results in this in the kernel serial log:
	 nd_pmem namespace0.0: region0 read-write, marking pmem0 read-write

with the read-only setting lost:
	$ blockdev --getro /dev/pmem0
	0

That's from bus.c nvdimm_revalidate_disk(), which always applies the
setting from nd_region (which is initially based on the ACPI NFIT
NVDIMM state flags not_armed bit).

In contrast, commit 20bd1d026aac ("scsi: sd: Keep disk read-only when
re-reading partition") fixed this issue for SCSI devices to preserve
the previous setting if it was set to read-only.

This patch modifies bus.c to preserve any previous read-only setting.
It also eliminates the kernel serial log print except for cases where
read-write is changed to read-only, so it doesn't print read-only to
read-only non-changes.

Signed-off-by: Robert Elliott <elliott@hpe.com>
---
 drivers/nvdimm/bus.c | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
index a64023690cad..87762afa45b0 100644
--- a/drivers/nvdimm/bus.c
+++ b/drivers/nvdimm/bus.c
@@ -566,14 +566,17 @@ int nvdimm_revalidate_disk(struct gendisk *disk)
 {
 	struct device *dev = disk_to_dev(disk)->parent;
 	struct nd_region *nd_region = to_nd_region(dev->parent);
-	const char *pol = nd_region->ro ? "only" : "write";
+	int disk_ro = get_disk_ro(disk);
 
-	if (nd_region->ro == get_disk_ro(disk))
+	/* upgrade to read-only if the region is read-only
+	 * preserve as read-only if the disk is already read-only
+	 */
+	if (disk_ro || nd_region->ro == disk_ro)
 		return 0;
 
-	dev_info(dev, "%s read-%s, marking %s read-%s\n",
-			dev_name(&nd_region->dev), pol, disk->disk_name, pol);
-	set_disk_ro(disk, nd_region->ro);
+	dev_info(dev, "%s read-only, marking %s read-only\n",
+			dev_name(&nd_region->dev), disk->disk_name);
+	set_disk_ro(disk, 1);
 
 	return 0;
 
-- 
2.14.3

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] nvdimm: preserve read-only setting for pmem devices
  2018-05-31 23:36 [PATCH] nvdimm: preserve read-only setting for pmem devices Robert Elliott
@ 2018-06-01  4:16 ` Dan Williams
  0 siblings, 0 replies; 2+ messages in thread
From: Dan Williams @ 2018-06-01  4:16 UTC (permalink / raw)
  To: Robert Elliott; +Cc: linux-nvdimm

On Thu, May 31, 2018 at 4:36 PM, Robert Elliott <elliott@hpe.com> wrote:
> The pmem driver don't honor a forced read-only setting for very long:
>         $ blockdev --setro /dev/pmem0
>         $ blockdev --getro /dev/pmem0
>         1
>
> followed by various commands like these:
>         $ blockdev --rereadpt /dev/pmem0
>         or
>         $ mkfs.ext4 /dev/pmem0
>
> results in this in the kernel serial log:
>          nd_pmem namespace0.0: region0 read-write, marking pmem0 read-write
>
> with the read-only setting lost:
>         $ blockdev --getro /dev/pmem0
>         0
>
> That's from bus.c nvdimm_revalidate_disk(), which always applies the
> setting from nd_region (which is initially based on the ACPI NFIT
> NVDIMM state flags not_armed bit).
>
> In contrast, commit 20bd1d026aac ("scsi: sd: Keep disk read-only when
> re-reading partition") fixed this issue for SCSI devices to preserve
> the previous setting if it was set to read-only.
>
> This patch modifies bus.c to preserve any previous read-only setting.
> It also eliminates the kernel serial log print except for cases where
> read-write is changed to read-only, so it doesn't print read-only to
> read-only non-changes.
>
> Signed-off-by: Robert Elliott <elliott@hpe.com>

Looks good to me. I'll also add the FIxes: tag and Cc: stable when applying.

One small nit below that I'll fixup when applying.

> ---
>  drivers/nvdimm/bus.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
> index a64023690cad..87762afa45b0 100644
> --- a/drivers/nvdimm/bus.c
> +++ b/drivers/nvdimm/bus.c
> @@ -566,14 +566,17 @@ int nvdimm_revalidate_disk(struct gendisk *disk)
>  {
>         struct device *dev = disk_to_dev(disk)->parent;
>         struct nd_region *nd_region = to_nd_region(dev->parent);
> -       const char *pol = nd_region->ro ? "only" : "write";
> +       int disk_ro = get_disk_ro(disk);
>
> -       if (nd_region->ro == get_disk_ro(disk))
> +       /* upgrade to read-only if the region is read-only
> +        * preserve as read-only if the disk is already read-only
> +        */
> +       if (disk_ro || nd_region->ro == disk_ro)
>                 return 0;

The comment style in libnvdimm for a multi-line comment starts with /*
on a line by itself.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-06-01  4:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-31 23:36 [PATCH] nvdimm: preserve read-only setting for pmem devices Robert Elliott
2018-06-01  4:16 ` Dan Williams

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).