From: Al Viro <viro@ZenIV.linux.org.uk>
To: Tom Spink <tspink@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] Introduce filesystem type tracking
Date: Tue, 20 May 2008 14:43:06 +0100 [thread overview]
Message-ID: <20080520134306.GA28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <7b9198260805200606u6ebc2681o8af7a8eebc1cb96@mail.gmail.com>
On Tue, May 20, 2008 at 02:06:42PM +0100, Tom Spink wrote:
[snip]
> I'm just adding people to CC here, but also I had a couple of thoughts
> after reviewing my own code.
>
> I see that do_kern_mount is encapsulated with the BKL, but would it be
> wise to introduce a lock (e.g. a mutex) now for reading and updating
> nr_mounts (and hence calling ->init), rather than wait for the BKL
> removal to come round here?
>
> Also, have I got all the cases where a filesystem is unmounted,
> because I now see umount_tree, and am wondering if decrementing the
> nr_mounts field should be done in here, in the loop of vfsmounts... or
> is it sufficient to leave it at the end of do_umount?
No, you have not and no, doing that anywhere near that layer is hopeless.
a) Instances of filesystem can easily outlive all vfsmounts,
let alone their attachment to namespaces.
b) What should happen if init is done in the middle of exit?
c) Why do we need to bother, anyway?
next prev parent reply other threads:[~2008-05-20 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 11:22 [RFC PATCH] Introduce filesystem type tracking Tom Spink
2008-05-20 13:06 ` Tom Spink
2008-05-20 13:43 ` Al Viro [this message]
2008-05-20 13:50 ` Tom Spink
2008-05-20 13:57 ` Christoph Hellwig
2008-05-20 15:18 ` Tom Spink
2008-05-20 15:34 ` Matthew Wilcox
2008-05-20 15:36 ` Tom Spink
2008-05-20 21:08 ` Tom Spink
2008-05-20 22:00 ` Matthew Wilcox
2008-05-20 22:22 ` Tom Spink
2008-05-21 14:49 ` Tom Spink
2008-05-21 9:42 ` Jan Engelhardt
2026-02-18 9:49 ` Christian Brauner
2026-02-19 5:51 ` Christoph Hellwig
2026-02-19 8:04 ` Christian Brauner
2026-02-19 8:45 ` Christian Brauner
2026-02-20 5:43 ` David Timber
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=20080520134306.GA28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tspink@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox