linux-kernel - Re: [PATCH] VFS: Fixup kerneldoc for generic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110706090014.d46bbbe3.rdunlap@xenotime.net>
Date:	Wed, 6 Jul 2011 09:00:14 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Tobias Klauser <tklauser@...tanz.ch>
Cc:	Alexander Viro <viro@...iv.linux.org.uk>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] VFS: Fixup kerneldoc for generic_permission()

On Fri,  1 Jul 2011 13:44:51 +0200 Tobias Klauser wrote:

> The flags parameter went away in
> 5c90c1601f00154f8695951469f25f33579272ed

What git tree is that commit ID in?

This patch applies to linux-next, right?

> Signed-off-by: Tobias Klauser <tklauser@...tanz.ch>
> ---
>  fs/namei.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/namei.c b/fs/namei.c
> index f181e4c..73fc34a 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -213,7 +213,6 @@ other_perms:
>   * generic_permission -  check for access rights on a Posix-like filesystem
>   * @inode:	inode to check access rights for
>   * @mask:	right to check for (%MAY_READ, %MAY_WRITE, %MAY_EXEC)
> - * @flags:	IPERM_FLAG_ flags.
>   *
>   * Used to check for read/write/execute permissions on a file.
>   * We use "fsuid" for this, letting us set arbitrary permissions
> -- 


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/