From: "Tom Spink" <tspink@gmail.com>
To: "Al Viro" <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] vfs: Introduce on-demand filesystem initialisation
Date: Mon, 2 Jun 2008 14:38:37 +0100 [thread overview]
Message-ID: <7b9198260806020638y7bb5ff19l416b329b22528ba9@mail.gmail.com> (raw)
In-Reply-To: <20080601153205.GM28946@ZenIV.linux.org.uk>
2008/6/1 Al Viro <viro@zeniv.linux.org.uk>:
> On Sun, Jun 01, 2008 at 03:51:54PM +0100, Tom Spink wrote:
>
>
> Occam's Razor...
>
> You've just serialized ->kill_sb() for given fs type (and made sure that
> if one gets stuck, _everything_ gets stuck). Moreover, you've serialized
> sget() against the same thing (i.e. pretty much each ->get_sb()).
>
> All of that (and a couple of new methods) is done for something that just
> plain does not belong to VFS. It's trivially doable in filesystem *and*
> it's about the objects with lifetimes that make sense only for filesystem
> itself.
Okay! Thanks for reviewing, anyway. :-)
--
Tom Spink
next prev parent reply other threads:[~2008-06-02 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 14:51 [RFC PATCH 0/2] On-demand Filesystem Initialisation Tom Spink
2008-06-01 14:51 ` [RFC PATCH 1/2] vfs: Introduce on-demand filesystem initialisation Tom Spink
2008-06-01 14:51 ` [RFC PATCH 2/2] xfs: Make XFS use the new file system init infrastructure Tom Spink
2008-06-01 15:32 ` [RFC PATCH 1/2] vfs: Introduce on-demand filesystem initialisation Al Viro
2008-06-02 13:38 ` Tom Spink [this message]
2008-06-02 1:58 ` [RFC PATCH 0/2] On-demand Filesystem Initialisation Dave Chinner
2008-06-02 13:39 ` Tom Spink
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=7b9198260806020638y7bb5ff19l416b329b22528ba9@mail.gmail.com \
--to=tspink@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).