linux-kernel - [PATCH ext4] ext4 crypto: ext4_xattr_encryption_context

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] [day] [month] [year] [list]

Message-ID: <20150116020713.GA50649@snb>
Date:	Fri, 16 Jan 2015 10:07:13 +0800
From:	kbuild test robot <fengguang.wu@...el.com>
To:	Michael Halcrow <mhalcrow@...gle.com>
Cc:	kbuild-all@...org, Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH ext4] ext4 crypto: ext4_xattr_encryption_context_set() can be
 static

fs/ext4/xattr_encryption.c:80:5: sparse: symbol 'ext4_xattr_encryption_context_set' was not declared. Should it be static?

Signed-off-by: Fengguang Wu <fengguang.wu@...el.com>
---
 xattr_encryption.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/ext4/xattr_encryption.c b/fs/ext4/xattr_encryption.c
index d03697a..851064a 100644
--- a/fs/ext4/xattr_encryption.c
+++ b/fs/ext4/xattr_encryption.c
@@ -77,7 +77,7 @@ static int ext4_xattr_encryption_set(struct dentry *dentry, const char *name,
  * Made as a separate function on purpose, so that setting this value from user
  * space tools is not available through generic set attribute path.
  */
-int ext4_xattr_encryption_context_set(struct dentry *dentry, const void *value,
+static int ext4_xattr_encryption_context_set(struct dentry *dentry, const void *value,
 				      size_t size, int flags, int type)
 {
 	return ext4_xattr_set(dentry->d_inode,
--
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/