linux-kernel - Re: [RFC 0/2] vfs / btrfs: add support for ustat()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 16 Jul 2014 23:34:12 +0200
From:	"Luis R. Rodriguez" <mcgrof@...e.com>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	viro@...iv.linux.org.uk, clm@...com, jbacik@...com,
	linux-fsdevel@...r.kernel.org, linux-btrfs@...r.kernel.org,
	linux-kernel@...r.kernel.org, jeffm@...e.com, fdmanana@...e.com
Subject: Re: [RFC 0/2] vfs / btrfs: add support for ustat()

On Tue, Jul 15, 2014 at 04:07:03PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@...e.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.
> 

Based on some private review I got this can be simplified leaving
the embedded the struct on the fs data structure and just using
it to expose it on the VFS. Will send a v2.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/