linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: FUSE: anyway to return different stat::st_dev inside one filesystem?
Date: Tue, 9 Nov 2021 01:49:07 -0800	[thread overview]
Message-ID: <YYpEE+Mi7msHCebP@infradead.org> (raw)
In-Reply-To: <a5c2941f-b3df-b811-a8a9-860309b03c32@gmx.com>

On Mon, Nov 08, 2021 at 10:22:16AM +0800, Qu Wenruo wrote:
> For kernel btrfs, it's not a big deal, as we will return different
> st_dev for each subvolume.

It is a big deal, as that behavior does break things and has been the
source of constant troubnle and discussion.  It needs to be fixed in
btrfs eventually and absolutely not spread any further.

      reply	other threads:[~2021-11-09  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08  2:22 FUSE: anyway to return different stat::st_dev inside one filesystem? Qu Wenruo
2021-11-09  9:49 ` Christoph Hellwig [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=YYpEE+Mi7msHCebP@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=quwenruo.btrfs@gmx.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).