From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Beata Michalska <b.michalska@samsung.com>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, kyungmin.park@samsung.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] ext4: Add pollable sysfs entry for block threshold events
Date: Fri, 13 Mar 2015 11:05:22 -0400 [thread overview]
Message-ID: <20150313150522.GA21922@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1503111314230.11156@localhost.localdomain>
On Wed, Mar 11, 2015 at 03:12:25PM +0100, Lukáš Czerner wrote:
>
> I though you were advocating for a solution independent on the file
> system. This is ext4 only solution, but I do not really have
> anything against this.
It would be nice if we could have a fs-independent solution so that we
don't have to support the ext4-specific interface forever. If we had
the thresholds set in struct super, and the file system were to call a
function defined in struct super_operations when the file system has
gotten too full, this wouldn't be all that hard.
The main issue is what is the proper generic way of notifying
userspace. Using a pollable sysfs file is one way, although problem
with that is we don't yet have a standardized place to locate where,
given a particular mounted file system / block device, where to find
its hierarchy in the sysfs tree. Right now we have
/sys/fs/<type>/... but that's owned by the file system and so it get's a
bit tricky to do something generic.
Other solutions might be to report file system full (and file system
corruption issues, etc.) via a netlink socket, or if we want to do
things in a systemd-complaint way, we could use the kernel-level dbus
approach which Greg K-H and company are pushing. :-)
- Ted
prev parent reply other threads:[~2015-03-13 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 10:16 [RFC] ext4: Add pollable sysfs entry for block threshold events Beata Michalska
2015-03-11 10:16 ` Beata Michalska
2015-03-11 14:12 ` Lukáš Czerner
2015-03-11 16:45 ` Beata Michalska
2015-03-11 17:49 ` Lukáš Czerner
2015-03-12 9:06 ` Beata Michalska
2015-03-13 15:05 ` Theodore Ts'o [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=20150313150522.GA21922@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=b.michalska@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.