From: Andrew Morton <akpm@osdl.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH] intrinsic automount and mountpoint degradation support
Date: Wed, 30 Jun 2004 12:57:13 -0700 [thread overview]
Message-ID: <20040630125713.36004088.akpm@osdl.org> (raw)
In-Reply-To: <31080.1088624498@redhat.com>
David Howells <dhowells@redhat.com> wrote:
>
> Here's a patch that I worked out with Al Viro that adds support for a
> filesystem (such as kAFS) to perform automounting intrinsically without the
> need for a userspace daemon. It also adds support for such mountpoints to be
> degraded at the filesystem's behest until they've been untouched long enough
> that they'll be removed.
Please don't try to add uncommented code to the kernel.
How does this work?
Why is autofs unsuitable?
Apart from documenting the major functions and data structures, comments
are also needed which describe the interpretation of ->mnt_count. This:
+ if (atomic_read(&mnt->mnt_count) == 2) {
is otherwise incomprehensible.
Apart from making the code maintainable, tasteful commentary and covering
documentation makes the patch review process much more fruitful. Please
have a think about that, and resend?
Thanks.
next prev parent reply other threads:[~2004-06-30 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 19:41 [PATCH] intrinsic automount and mountpoint degradation support David Howells
2004-06-30 19:57 ` Andrew Morton [this message]
2004-07-01 12:59 ` [PATCH] intrinsic automount and mountpoint degradation support [try #2] David Howells
-- strict thread matches above, loose matches on Subject: below --
2004-06-30 19:35 [PATCH] intrinsic automount and mountpoint degradation support David Howells
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=20040630125713.36004088.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--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 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.