All of lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] NVMe: Fix FS mount issue (hot-remove followed by hot-add)
Date: Thu, 11 Dec 2014 08:20:44 -0700	[thread overview]
Message-ID: <5489B64C.5020209@kernel.dk> (raw)
In-Reply-To: <alpine.LNX.2.00.1412101949260.4026@localhost.lm.intel.com>

On 12/10/2014 01:00 PM, Keith Busch wrote:
> On Wed, 10 Dec 2014, Indraneel M wrote:
>> 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.
>>
>> Signed-off-by: Indraneel M <indraneel.m at samsung.com>
>
> Acked-by: Keith Busch <keith.busch at intel.com>
>
> Now where is this going? It won't apply to linux-block/for-next (though
> it is a trivial manual merge), which I think is where the 3.19 pull
> request to mainline will come from. I hope these trees get synced up
> soon so we don't have these fragmented drivers.

He sent a for-3.19/drivers relevant patch too - I'll add your acked by 
and queue that up.

-- 
Jens Axboe

      reply	other threads:[~2014-12-11 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 14:25 [PATCH] NVMe: Fix FS mount issue (hot-remove followed by hot-add) Indraneel M
2014-12-10 20:00 ` Keith Busch
2014-12-11 15:20   ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5489B64C.5020209@kernel.dk \
    --to=axboe@kernel.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.