From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
viro@zeniv.linux.org.uk, clm@fb.com, jbacik@fb.com,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, jeffm@suse.com, fdmanana@suse.com
Subject: Re: [RFC 0/2] vfs / btrfs: add support for ustat()
Date: Wed, 16 Jul 2014 21:13:19 +0200 [thread overview]
Message-ID: <20140716191319.GN10393@wotan.suse.de> (raw)
In-Reply-To: <20140716052919.GA3486@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Tue, Jul 15, 2014 at 10:29:19PM -0700, Christoph Hellwig wrote:
> Isn't this the problem again the btrfs uses different assignments for
> st_dev than s_dev? I don't even want to think about a mess like this
> before that is fixed.
As much as I'd like to see that happen based on discussions so far its unclear
if this is going to be possible unless strong commitment is reached... so what
this tried to do was to take the other way around the problem, by slowly
shifting out junk. Although I'm frankly new to this -- I think this approach might
be more feasible over time. As I see it this is an extension to Al's original
commit 0ee5dc676 but more in line with how they are really are used and exposes
more information to the VFS. As it stands now other filesystems can pop up and
do similar things, this at least extends the original API to fit the use case a
bit more closely to how its used and allows more room to grow.
Luis
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2014-07-16 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 23:07 [RFC 0/2] vfs / btrfs: add support for ustat() Luis R. Rodriguez
2014-07-15 23:07 ` [RFC 1/2] fs/super.c: add new super block sub devices super_block_dev Luis R. Rodriguez
2014-07-15 23:07 ` [RFC 2/2] btrfs: use the new VFS super_block_dev Luis R. Rodriguez
2014-07-16 5:29 ` [RFC 0/2] vfs / btrfs: add support for ustat() Christoph Hellwig
2014-07-16 19:13 ` Luis R. Rodriguez [this message]
2014-07-16 21:34 ` Luis R. Rodriguez
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=20140716191319.GN10393@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=clm@fb.com \
--cc=fdmanana@suse.com \
--cc=hch@infradead.org \
--cc=jbacik@fb.com \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--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 NNTP newsgroup(s).