NVMe: Fix FS mount issue (hot-remove followed by hot-add)
authorIndraneel M <indraneel.m@samsung.com>
Thu, 11 Dec 2014 15:24:18 +0000 (08:24 -0700)
committerJens Axboe <axboe@fb.com>
Thu, 11 Dec 2014 15:24:18 +0000 (08:24 -0700)
commit285dffc9101244ac65c29672a1fb3fe614b52238
tree1220bf2e24fe8aa514bb1d6ee68b785e31e2da6b
parentd8ead9b763cab553f82a6f16015d3ace5f9c6653
NVMe: Fix FS mount issue (hot-remove followed by hot-add)

After Hot-remove of a device with a mounted partition,
when the device is hot-added again, the new node reappears
as nvme0n1. Mounting this new node fails with the error:

mount: mount /dev/nvme0n1p1 on /mnt failed: File exists.

The old nodes's FS entries still exist and the kernel can't re-create
procfs and sysfs entries for the new node with the same name.
The patch fixes this issue.

Acked-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Indraneel M <indraneel.m@samsung.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
drivers/block/nvme-core.c