From: Christoph Hellwig <hch@infradead.org>
To: Karel Zak <kzak@redhat.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: btrfs mount failure with context option and latest mount command
Date: Wed, 18 Jan 2023 22:13:22 -0800 [thread overview]
Message-ID: <Y8jfgsNbcKTLdnmQ@infradead.org> (raw)
In-Reply-To: <20230117164234.znsa4oeoovcdpntu@ws.net.home>
On Tue, Jan 17, 2023 at 05:42:34PM +0100, Karel Zak wrote:
> It's a serious issue if btrfs is not ready for the new kernel fsconfig
> interface. I guess libmount cannot do anything else in this case
> (well, we can switch back to classic mount(2), but it sounds as a
> wrong solution).
Unfortunately a lot of file systems haven't been converted to the
fsconfig code yet, it's another case of adding new infrastructure to
the kernel then not following up on the conversion, and all too common
patter unfortunately :( btrfs might be the only major disk file system,
but there's lot of others.
prev parent reply other threads:[~2023-01-19 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 10:15 btrfs mount failure with context option and latest mount command Shinichiro Kawasaki
2023-01-17 16:42 ` Karel Zak
2023-01-19 6:13 ` 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=Y8jfgsNbcKTLdnmQ@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=dhowells@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=util-linux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).