From: Valerie Aurora <vaurora@redhat.com>
To: Nick Piggin <npiggin@kernel.dk>
Cc: Al Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 03/10] apparmor: use task path helpers
Date: Tue, 17 Aug 2010 18:59:41 -0400 [thread overview]
Message-ID: <20100817225941.GM5556@shell> (raw)
In-Reply-To: <20100817184120.622515715@kernel.dk>
On Wed, Aug 18, 2010 at 04:37:32AM +1000, Nick Piggin wrote:
> apparmor: use task path helpers
>
> Signed-off-by: Nick Piggin <npiggin@kernel.dk>
>
> ---
> BTW, argh! dcache_lock! Why does everything have to invent its own reverse
> path lookup crud and hide it away in its own code? Also, admire the rest of
> this beautiful function.
>
> ---
> security/apparmor/path.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> Index: linux-2.6/security/apparmor/path.c
> ===================================================================
> --- linux-2.6.orig/security/apparmor/path.c 2010-08-18 04:04:02.000000000 +1000
> +++ linux-2.6/security/apparmor/path.c 2010-08-18 04:04:29.000000000 +1000
> @@ -62,19 +62,14 @@ static int d_namespace_path(struct path
> int deleted, connected;
> int error = 0;
>
> - /* Get the root we want to resolve too */
> + /* Get the root we want to resolve too, released below */
> if (flags & PATH_CHROOT_REL) {
> /* resolve paths relative to chroot */
> - read_lock(¤t->fs->lock);
> - root = current->fs->root;
> - /* released below */
> - path_get(&root);
> - read_unlock(¤t->fs->lock);
> + get_fs_root(current->fs, &root);
> } else {
> /* resolve paths relative to namespace */
> root.mnt = current->nsproxy->mnt_ns->root;
> root.dentry = root.mnt->mnt_root;
> - /* released below */
> path_get(&root);
> }
Gosh, maybe this VFS stuff isn't as hard as I thought! This one's
easy to review too. :)
Looks good.
Reviewed-by: Valerie Aurora <vaurora@redhat.com>
-VAL
next prev parent reply other threads:[~2010-08-17 22:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 18:37 [patch 00/10] first set of vfs scale patches Nick Piggin
2010-08-17 18:37 ` [patch 01/10] fs: fix do_lookup false negative Nick Piggin
2010-08-17 22:45 ` Valerie Aurora
2010-08-17 23:04 ` Sage Weil
2010-08-18 13:41 ` Andi Kleen
2010-08-17 18:37 ` [patch 02/10] fs: dentry allocation consolidation Nick Piggin
2010-08-17 22:45 ` Valerie Aurora
2010-08-17 18:37 ` [patch 03/10] apparmor: use task path helpers Nick Piggin
2010-08-17 22:59 ` Valerie Aurora [this message]
2010-08-17 18:37 ` [patch 04/10] fs: fs_struct rwlock to spinlock Nick Piggin
2010-08-17 23:14 ` Valerie Aurora
2010-08-20 10:05 ` Nick Piggin
2010-08-17 18:37 ` [patch 05/10] fs: remove extra lookup in __lookup_hash Nick Piggin
2010-08-18 13:57 ` Andi Kleen
2010-08-18 21:13 ` Andi Kleen
2010-08-18 19:34 ` Valerie Aurora
2010-08-17 18:37 ` [patch 06/10] fs: cleanup files_lock locking Nick Piggin
2010-08-18 19:46 ` Valerie Aurora
2010-08-17 18:37 ` [patch 07/10] tty: fix fu_list abuse Nick Piggin
2010-08-17 18:37 ` [patch 08/10] lglock: introduce special lglock and brlock spin locks Nick Piggin
2010-08-17 18:37 ` [patch 09/10] fs: scale files_lock Nick Piggin
2010-08-17 18:37 ` [patch 10/10] fs: brlock vfsmount_lock Nick Piggin
2010-08-18 14:05 ` Andi Kleen
2010-08-20 10:09 ` Nick Piggin
2010-08-17 21:14 ` [patch 00/10] first set of vfs scale patches Al Viro
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=20100817225941.GM5556@shell \
--to=vaurora@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--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).