Partitions and end-to-end protection

Keith Busch keith.busch at intel.com
Mon Jul 13 12:16:25 PDT 2015


On Mon, 13 Jul 2015, Paul Grabinar wrote:
> What seems to be happening is that the driver starts off by setting the
> capacity to zero whilst it validates the meta-data configuration and
> then sets the real size after this validation. However, setting the
> capacity does not seem to be enough to tell the kernel to re-read the
> partition table.

The driver did it this way because we need a disk allocated before we can
subscribe to block integrity extensions. I think we can fix the partition
issue by making a call to blkdev_reread_part() right after the second
revalidate_disk if the namespace is a meta-data formatted. I'll test it
out and post a patch if it works out.



More information about the Linux-nvme mailing list