linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: viro@zeniv.linux.org.uk, clm@fb.com, jbacik@fb.com
Cc: linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, jeffm@suse.com, fdmanana@suse.com,
	"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: [RFC 0/2] vfs / btrfs: add support for ustat()
Date: Tue, 15 Jul 2014 16:07:03 -0700	[thread overview]
Message-ID: <1405465625-1122-1-git-send-email-mcgrof@do-not-panic.com> (raw)

From: "Luis R. Rodriguez" <mcgrof@suse.com>

ustat() does not work for btrfs, the reason is the VFS layer
cannot get to the super block from the anonymous bdevs. The
way these are used within btrfs though are to actually use a
series of them per superblock. This modifies the way the
VFS exposes these bdevs by pegging them onto the super
block on a linked list. This should also allow us to grow
the subdevices on the super block with any other information
that might be better suited underneath so that the VFS
layer is aware. If this approach is reasonable then perhaps
we should next remove the exported symbol for get_anon_bdev()
as btrfs was the only user.

Luis R. Rodriguez (2):
  fs/super.c: add new super block sub devices super_block_dev
  btrfs: use the new VFS super_block_dev

 fs/btrfs/ctree.h   |  7 ++---
 fs/btrfs/disk-io.c | 10 +++---
 fs/btrfs/inode.c   |  2 +-
 fs/super.c         | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++++--
 include/linux/fs.h | 10 ++++++
 5 files changed, 106 insertions(+), 13 deletions(-)

-- 
2.0.1

             reply	other threads:[~2014-07-15 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 23:07 Luis R. Rodriguez [this message]
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
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=1405465625-1122-1-git-send-email-mcgrof@do-not-panic.com \
    --to=mcgrof@do-not-panic.com \
    --cc=clm@fb.com \
    --cc=fdmanana@suse.com \
    --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@suse.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).