public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: provide slaves/holders links for multipath devices
Date: Fri, 16 Nov 2018 14:08:03 +0100	[thread overview]
Message-ID: <20181116130805.16225-1-hch@lst.de> (raw)

Hi all,

a while ago Thadeu reported installer problems because nvme multipath
didn't provide slaves/holders links for the underlying devices.

This is because for one Tejun said the API shall not be used for new
users, but also because it currently hangs off the block_device
structure, which has a too short lifetime.

This series ignores Tejuns advice given that these links are the
defacto API for stacked block devices, moves the tracking to struct
hd_struct, and makes it work on NVMe multipath.

             reply	other threads:[~2018-11-16 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 13:08 Christoph Hellwig [this message]
2018-11-16 13:08 ` [PATCH 1/2] block: move holder tracking from struct block_device to hd_struct Christoph Hellwig
2018-11-28  1:59   ` Sagi Grimberg
2018-11-16 13:08 ` [PATCH 2/2] nvme: create slaves/holder entries for multipath devices Christoph Hellwig
2018-11-28  1:59   ` Sagi Grimberg
2018-11-28  8:38   ` Thadeu Lima de Souza Cascardo
2018-12-06 15:44     ` Christoph Hellwig
2018-12-06 16:48       ` Thadeu Lima de Souza Cascardo

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=20181116130805.16225-1-hch@lst.de \
    --to=hch@lst.de \
    /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