diff options
author | Robert Elliott <elliott@hpe.com> | 2018-06-01 02:36:36 +0300 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2018-06-01 07:07:33 +0300 |
commit | 254a4cd50b9fe2291a12b8902e08e56dcc4e9b10 (patch) | |
tree | ddca38d2bb5c822e2c17aa2cd69fff983b5f2b74 /Kbuild | |
parent | b04e217704b7f879c6b91222b066983a44a7a09f (diff) | |
download | linux-254a4cd50b9fe2291a12b8902e08e56dcc4e9b10.tar.xz |
linvdimm, pmem: Preserve read-only setting for pmem devices
The pmem driver does not 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.
Cc: <stable@vger.kernel.org>
Fixes: 581388209405 ("libnvdimm, nfit: handle unarmed dimms, mark namespaces read-only")
Signed-off-by: Robert Elliott <elliott@hpe.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions