From: Goffredo Baroncelli <kreijack@inwind.it>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v0 0/4] BTRFS sysfs support
Date: Thu, 23 Aug 2012 14:12:36 +0200 [thread overview]
Message-ID: <20120823120505.12203.11658.stgit@venice.bhome> (raw)
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 (the last one) which contains an update of the btrfs.txt file.
The goal of this first 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 make some action: for example to change the
label of a filesystem.
Comments are welcome.
BR
G.Baroncelli
---
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 | 933 ++++++++++++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/sysfs.h | 31 ++
fs/btrfs/volumes.c | 15 +
5 files changed, 986 insertions(+), 6 deletions(-)
create mode 100644 fs/btrfs/sysfs.h
next reply other threads:[~2012-08-23 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 12:12 Goffredo Baroncelli [this message]
2012-08-23 12:12 ` [PATCH v0 1/4] Add support for sysfs to btrfs Goffredo Baroncelli
2012-08-23 14:01 ` Stefan Behrens
2012-08-23 12:13 ` [PATCH v0 2/4] Add hook " Goffredo Baroncelli
2012-08-23 12:13 ` [PATCH v0 3/4] Add a new Kconfig section to enable or disable the sysfs Goffredo Baroncelli
2012-08-23 12:13 ` [PATCH v0 4/4] Btrfs sysfs support documentation Goffredo Baroncelli
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=20120823120505.12203.11658.stgit@venice.bhome \
--to=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 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).