linux-kernel - Re: [PATCH 1/1 RESEND] fs/ceph/export.c: add static to local function

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 16 Jun 2014 17:02:17 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Fabian Frederick <fabf@...net.be>
cc:	Fengguang Wu <fengguang.wu@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	akpm <akpm@...ux-foundation.org>, sage <sage@...tank.com>
Subject: Re: [PATCH 1/1 RESEND] fs/ceph/export.c: add static to local
 function

On Sun, 15 Jun 2014, Fabian Frederick wrote:

> ceph_get_parent is only used in fs/ceph/export.c
> 
> Cc: Sage Weil <sage@...tank.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Signed-off-by: Fabian Frederick <fabf@...net.be>
> ---
>  fs/ceph/export.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/ceph/export.c b/fs/ceph/export.c
> index 00d6af6..8d7d782 100644
> --- a/fs/ceph/export.c
> +++ b/fs/ceph/export.c
> @@ -169,7 +169,7 @@ static struct dentry *__get_parent(struct super_block *sb,
>  	return dentry;
>  }
>  
> -struct dentry *ceph_get_parent(struct dentry *child)
> +static struct dentry *ceph_get_parent(struct dentry *child)
>  {
>  	/* don't re-export snaps */
>  	if (ceph_snap(child->d_inode) != CEPH_NOSNAP)

Not sure what tree you're modifying, this is fixed by commit e84be11c5360 
("ceph: ceph_get_parent() can be static") in Linus's tree.
--
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/