From: Andrew Morton <akpm@linux-foundation.org>
To: Ian Kent <raven@themaw.net>
Cc: linux-kernel@vger.kernel.org, autofs@linux.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] autofs4 - detect invalid direct mount requests
Date: Tue, 1 Jul 2008 14:17:15 -0700 [thread overview]
Message-ID: <20080701141715.62a2132b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080620051301.9988.94307.stgit@raven.themaw.net>
On Fri, 20 Jun 2008 13:13:03 +0800
Ian Kent <raven@themaw.net> wrote:
> autofs v5 dierct and offset mounts within an autofs filesystem are
> triggered by existing autofs triger mounts so the mount point dentry
> must be positive. If the mount point dentry is negative then the
> trigger doesn't exist so we can return fail immediately.
>
> Signed-off-by: Ian Kent <raven@themaw.net>
>
> ---
>
> fs/autofs4/waitq.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
>
> diff --git a/fs/autofs4/waitq.c b/fs/autofs4/waitq.c
> index cd21fd4..ae637d9 100644
> --- a/fs/autofs4/waitq.c
> +++ b/fs/autofs4/waitq.c
> @@ -307,6 +307,10 @@ int autofs4_wait(struct autofs_sb_info *sbi, struct dentry *dentry,
> if (sbi->catatonic)
> return -ENOENT;
>
> + if (!dentry->d_inode &&
> + (sbi->type & (AUTOFS_TYPE_DIRECT | AUTOFS_TYPE_OFFSET)))
> + return -ENOENT;
> +
> name = kmalloc(NAME_MAX + 1, GFP_KERNEL);
> if (!name)
> return -ENOMEM;
A good changelog would allow little old me to determine whether this
patch should be merged into 2.6.25 and/or 2.6.26 and/or 2.6.27. This
wasn't a good changelog :(
next prev parent reply other threads:[~2008-07-01 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 5:13 [PATCH] autofs4 - detect invalid direct mount requests Ian Kent
2008-06-20 13:00 ` Jeff Moyer
2008-06-20 13:12 ` Ian Kent
2008-07-02 13:46 ` Ian Kent
2008-07-01 21:17 ` Andrew Morton [this message]
2008-07-02 8:59 ` Ian Kent
2008-07-02 13:42 ` Jeff Moyer
2008-07-02 13:50 ` Ian Kent
2008-07-02 16:54 ` Andrew Morton
2008-07-03 1:57 ` Ian Kent
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=20080701141715.62a2132b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=autofs@linux.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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).