Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: paul.grabinar@ranbarg.com (Paul Grabinar)
Subject: Partitions and end-to-end protection
Date: Mon, 13 Jul 2015 20:22:45 +0100	[thread overview]
Message-ID: <55A41005.9060808@ranbarg.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1507131909210.15930@localhost.lm.intel.com>

On 13/07/15 20:16, Keith Busch wrote:
> 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.
>

Thanks Keith.

  reply	other threads:[~2015-07-13 19:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 18:50 Partitions and end-to-end protection Paul Grabinar
2015-07-13 19:16 ` Keith Busch
2015-07-13 19:22   ` Paul Grabinar [this message]
2015-07-14 18:06   ` Christoph Hellwig
2015-07-14 18:13     ` Dan Williams
2015-07-14 18:15       ` Christoph Hellwig
2015-07-14 18:25         ` Dan Williams
2015-07-14 18:41     ` Martin K. Petersen
2015-07-14 18:43       ` Christoph Hellwig
2015-07-14 18:58         ` Martin K. Petersen
2015-07-14 19:25           ` Keith Busch
2015-07-14 19:38             ` Martin K. Petersen
2015-07-14 19:45               ` Keith Busch
2015-07-14 20:07                 ` Martin K. Petersen
2015-07-14 20:14                   ` Keith Busch

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=55A41005.9060808@ranbarg.com \
    --to=paul.grabinar@ranbarg.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox