From: Ric Wheeler <rwheeler@redhat.com>
To: Valerie Aurora <vaurora@redhat.com>
Cc: Dave Chinner <david@fromorbit.com>,
Andreas Dilger <adilger@sun.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>,
tytso@mit.edu, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [REPOST][PATCH][RFC] vfs: add message print mechanism for the mount/umount into the VFS layer
Date: Fri, 15 Jan 2010 13:43:42 -0500 [thread overview]
Message-ID: <4B50B75E.1050802@redhat.com> (raw)
In-Reply-To: <20100115180722.GD3482@shell>
On 01/15/2010 01:07 PM, Valerie Aurora wrote:
> On Fri, Jan 15, 2010 at 12:24:21PM +1100, Dave Chinner wrote:
>
>> FWIW, having a general event channel for reporting filesystem events like
>> mount, enospc, corruption, etc makes a lot of sense to me.
>> Especially from the point of view that they can be also be tied into
>> automated filesystem test harnesses easily....
>>
> Mmm, yummy! Is this perhaps a topic for the next file systems workshop?
>
> (When _is_ the next file systems workshop?)
>
> -VAL
>
I think that the current plan is to have it next to the LinuxCon event
in Boston in early August....
The VM people are looking to do a mini-summit there as well and we were
talking about getting together with them during part of the time,
Ric
next prev parent reply other threads:[~2010-01-15 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 6:48 [REPOST][PATCH][RFC] vfs: add message print mechanism for the mount/umount into the VFS layer Toshiyuki Okajima
2010-01-14 8:14 ` Al Viro
2010-01-14 9:03 ` Mike Mestnik
2010-01-14 15:33 ` Andreas Dilger
2010-01-15 1:24 ` Dave Chinner
2010-01-15 4:36 ` Andreas Dilger
2010-01-15 8:31 ` Toshiyuki Okajima
2010-01-15 11:02 ` Dave Chinner
2010-01-15 11:44 ` Mike Mestnik
2010-01-15 13:15 ` Dave Chinner
2010-01-15 18:07 ` Valerie Aurora
2010-01-15 18:43 ` Ric Wheeler [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-04 4:49 [REPOST] [PATCH][RFC] " Toshiyuki Okajima
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=4B50B75E.1050802@redhat.com \
--to=rwheeler@redhat.com \
--cc=adilger@sun.com \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=toshi.okajima@jp.fujitsu.com \
--cc=tytso@mit.edu \
--cc=vaurora@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
/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.