linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Yi Zhang <yi.zhang@redhat.com>, linux-nvme@lists.infradead.org
Subject: Re: incorrect sysfs reported by realpath for nvme disk when nvme-core:multipath enabled
Date: Sat, 14 Sep 2019 09:19:14 -0600	[thread overview]
Message-ID: <20190914151913.GA562@keith-busch> (raw)
In-Reply-To: <a24713ad-e907-2cfd-b1da-cef552c29b14@grimberg.me>

On Fri, Sep 13, 2019 at 11:43:40AM -0700, Sagi Grimberg wrote:
> > This was confusing to enough people that we've since changed the naming
> > to something people expect to see, but that's staged in 5.4. Given the
> > number of people who find this confusing, this might be worth making a
> > stable patch.
> 
> I agree here.

Okay, I'll forward the commit to stable once merged to mainline. I don't
think we can count on the stable bot to pick this one up. We only need
this back to 4.19 as all the previous stables with this naming scheme
have be EOL'ed.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2019-09-14 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1753358694.11967186.1568394608486.JavaMail.zimbra@redhat.com>
2019-09-13 17:40 ` incorrect sysfs reported by realpath for nvme disk when nvme-core:multipath enabled Yi Zhang
2019-09-13 17:56   ` Keith Busch
2019-09-13 18:43     ` Sagi Grimberg
2019-09-14 15:19       ` Keith Busch [this message]
2019-09-16  9:30         ` Yi Zhang

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=20190914151913.GA562@keith-busch \
    --to=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=yi.zhang@redhat.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;
as well as URLs for NNTP newsgroup(s).