diff options
| author | Vishal Verma <vishal.l.verma@intel.com> | 2018-03-05 16:56:13 -0700 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2018-03-07 13:50:09 -0800 |
| commit | 3ffb0ba9b567a8efb9a04ed3d1ec15ff333ada22 (patch) | |
| tree | 7376fdac1871e04829439c00cbd2ad83ce88dc6b /drivers/nvdimm/pfn_devs.c | |
| parent | 167f5594b5efa20a26ff03b3424f793887e6b448 (diff) | |
| download | linux-stable-3ffb0ba9b567a8efb9a04ed3d1ec15ff333ada22.tar.gz linux-stable-3ffb0ba9b567a8efb9a04ed3d1ec15ff333ada22.tar.bz2 linux-stable-3ffb0ba9b567a8efb9a04ed3d1ec15ff333ada22.zip | |
libnvdimm, {btt, blk}: do integrity setup before add_disk()
Prior to 25520d55cdb6 ("block: Inline blk_integrity in struct gendisk")
we needed to temporarily add a zero-capacity disk before registering for
blk-integrity. But adding a zero-capacity disk caused the partition
table scanning to bail early, and this resulted in partitions not coming
up after a probe of the BTT or blk namespaces.
We can now register for integrity before the disk has been added, and
this fixes the rescan problems.
Fixes: 25520d55cdb6 ("block: Inline blk_integrity in struct gendisk")
Reported-by: Dariusz Dokupil <dariusz.dokupil@intel.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/nvdimm/pfn_devs.c')
0 files changed, 0 insertions, 0 deletions