All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hanabishi <i.r.e.c.c.a.k.u.n+kernel.org@gmail.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: add "/dev/root" exception for device path update
Date: Sun, 13 Sep 2026 14:35:57 +0000	[thread overview]
Message-ID: <9a889cf5-4e47-4f6f-b8ab-4c65b2f82e3c@gmail.com> (raw)
In-Reply-To: <3e3164206d23ef991b9bd76dab6706238592cfb0.1789202516.git.wqu@suse.com>

I confirm that this patch fixes the '/dev/root' issue for me. Thank you.

> To be honest, this is a user space problem: no one should trust the
> device path shown in mount, only the device number.
There are too many userspace applications that simply don't know/care about such edge cases.
I'll try to report the situation where I can though.


  reply	other threads:[~2026-09-13 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12  8:42 [PATCH] btrfs: add "/dev/root" exception for device path update Qu Wenruo
2026-09-13 14:35 ` Hanabishi [this message]
2026-09-13 21:40   ` Qu Wenruo

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=9a889cf5-4e47-4f6f-b8ab-4c65b2f82e3c@gmail.com \
    --to=i.r.e.c.c.a.k.u.n+kernel.org@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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 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.