From: Goffredo Baroncelli <kreijack@libero.it>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v1 0/4] BTRFS sysfs support
Date: Fri, 24 Aug 2012 16:12:23 +0200 [thread overview]
Message-ID: <50378BC7.9060508@libero.it> (raw)
In-Reply-To: <20120824135322.20478.88578.stgit@venice.bhome>
You can pull the source from the following repo:
http://cassiopea.homelinux.net/git/btrfs-unstable.git
branch
sysfs
thanks.
G.Baroncelli
On 08/24/2012 03:58 PM, Goffredo Baroncelli wrote:
> Hi all,
> The following series restores the BTRFS sysfs support. My idea is to
> exporting some information via sysfs to get rid of some ioctl(s) which
> are particular solution of a more general problem: exporting information
> from kernel space to user space.
>
> These patches export basically the fields of the following structure:
> - btrfs_device
> - btrfs_fs_info
> - btrfs_fs_devices
>
> You can read more about which information are exported reading the
> patch which contains an update of the btrfs.txt file (the last one).
>
> The goal of this attempt is to collect comments relating to
> which information we should export and which not or the sysfs structure.
>
> For now these information are read-only. In the future we could
> consider the idea to allow updates: for example to change the
> label of a filesystem.
>
> Comments are welcome.
> BR
> G.Baroncelli
>
>
> Changelog:
>
> v0: First issue
> v1: Source cleanup and replacing of the printk with pr_info/pr_warn/
> pr_crit
>
> ---
>
> Goffredo Baroncelli (4):
> Add support for sysfs to btrfs.
> Add hook for sysfs to btrfs.
> Add a new Kconfig section to enable or disable the sysfs.
> Btrfs sysfs support documentation.
>
>
> fs/btrfs/Kconfig | 9
> fs/btrfs/super.c | 4
> fs/btrfs/sysfs.c | 938 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/btrfs/sysfs.h | 31 ++
> fs/btrfs/volumes.c | 10 -
> 5 files changed, 986 insertions(+), 6 deletions(-)
> create mode 100644 fs/btrfs/sysfs.h
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> .
>
prev parent reply other threads:[~2012-08-24 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 13:58 [PATCH v1 0/4] BTRFS sysfs support Goffredo Baroncelli
2012-08-24 13:58 ` [PATCH v1 1/4] Add support for sysfs to btrfs Goffredo Baroncelli
2012-08-24 13:59 ` [PATCH v1 2/4] Add hook " Goffredo Baroncelli
2012-08-24 13:59 ` [PATCH v1 3/4] Add a new Kconfig section to enable or disable the sysfs Goffredo Baroncelli
2012-08-24 13:59 ` [PATCH v1 4/4] Btrfs sysfs support documentation Goffredo Baroncelli
2012-08-24 14:12 ` Goffredo Baroncelli [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=50378BC7.9060508@libero.it \
--to=kreijack@libero.it \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.