From: Christoph Hellwig <hch@infradead.org>
To: raven@themaw.net
Cc: Andrew Morton <akpm@osdl.org>,
viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-rc1-mm1
Date: Wed, 21 Apr 2004 15:56:34 +0100 [thread overview]
Message-ID: <20040421155634.A6736@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404212135520.3740@donald.themaw.net>; from raven@themaw.net on Wed, Apr 21, 2004 at 09:52:01PM +0800
On Wed, Apr 21, 2004 at 09:52:01PM +0800, raven@themaw.net wrote:
> > On Wed, Apr 21, 2004 at 08:39:59PM +0800, raven@themaw.net wrote:
> > > While I understand the motive for not exporting the lock the question of
> > > how one should obtain vfsmount structs when needed remains?
> >
> > You shouldn't.
> >
>
> Shouldn't need them?
Exactly.
> But your point is that they shouldn't need to be used and an different
> design is should be used, right.
>
> Could make life hard for the automounter.
> Possibly somewhat harder to solve the remaining limitations of autofs.
> But I haven't got a clear enough picture of what's needed yet (still).
>
> I guess your point is that these services should reside in the VFS proper?
If you ask me much of what autofs does should reside in the VFS, namely
triggering userspace upcalls as soon someone enters a special trigger
(aka delayed mountpount) directory and expiry of vfsmounts.
next prev parent reply other threads:[~2004-04-21 15:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 6:01 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:29 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 6:42 ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-19 6:49 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 7:06 ` 2.6.6-rc1-mm1 William Lee Irwin III
2004-04-19 18:39 ` bitmap, cpumask_arith (was: 2.6.6-rc1-mm1) Paul Jackson
2004-04-20 21:17 ` Paul Jackson
2004-04-20 21:38 ` William Lee Irwin III
2004-04-19 6:58 ` 2.6.6-rc1-mm1 Nick Piggin
2004-04-19 9:13 ` 2.6.6-rc1-mm1 failure: kmod.o didn't compile with module-less setup Helge Hafting
2004-04-19 9:17 ` Andrew Morton
2004-04-19 15:26 ` 2.6.6-rc1-mm1 (compile stats) John Cherry
2004-04-19 19:25 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-20 1:13 ` 2.6.6-rc1-mm1 Ian Kent
2004-04-20 1:26 ` 2.6.6-rc1-mm1 Andrew Morton
2004-04-21 9:08 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:31 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:18 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:34 ` 2.6.6-rc1-mm1 raven
2004-04-21 15:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 16:09 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 12:39 ` 2.6.6-rc1-mm1 raven
2004-04-21 13:19 ` 2.6.6-rc1-mm1 Christoph Hellwig
2004-04-21 13:52 ` 2.6.6-rc1-mm1 raven
2004-04-21 14:56 ` Christoph Hellwig [this message]
2004-04-21 15:39 ` 2.6.6-rc1-mm1 raven
2004-04-20 14:27 ` 2.6.6-rc1-mm1 raven
2004-04-20 15:06 ` 2.6.6-rc1-mm1 Rik van Riel
2004-04-21 7:37 ` 2.6.6-rc1-mm1 Sean Neakums
2004-04-21 12:16 ` 2.6.6-rc1-mm1 Hugh Dickins
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=20040421155634.A6736@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.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
all inboxes | Powered by JetHome®