linux-kernel - [PATCH] KEYS: fix macro

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

Date:	Wed, 02 Jan 2008 15:10:12 +0000
From:	David Howells <dhowells@...hat.com>
To:	torvalds@...l.org, akpm@...ux-foundation.org
CC:	Sebastian Siewior <sebastian@...akpoint.cc>, dhowells@...hat.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH] KEYS: fix macro


From: Sebastian Siewior <sebastian@...akpoint.cc>

Commit 664cceb0093b755739e56572b836a99104ee8a75 changed the
parameters of the function make_key_ref(). The macros that
are used in case CONFIG_KEY is not defined did not change.

Cc: David Howells <dhowells@...hat.com>
Signed-off-by: Sebastian Siewior <sebastian@...akpoint.cc>
Acked-by: David Howells <dhowells@...hat.com>
---

I found this while compile testing some files with a broken .config
file. Currently there is no user of make_key_ref() that does not select
CONFIG_KEY via Kconfig. However you may want to include this patch in
your new batch :)

 include/linux/key.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/linux/key.h b/include/linux/key.h
index fcdbd5e..a70b8a8 100644
--- a/include/linux/key.h
+++ b/include/linux/key.h
@@ -290,7 +290,7 @@ extern void key_init(void);
 #define key_get(k) 			({ NULL; })
 #define key_put(k)			do { } while(0)
 #define key_ref_put(k)			do { } while(0)
-#define make_key_ref(k)			({ NULL; })
+#define make_key_ref(k, p)			({ NULL; })
 #define key_ref_to_ptr(k)		({ NULL; })
 #define is_key_possessed(k)		0
 #define alloc_uid_keyring(u,c)		0
-- 
1.5.3.7
--
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/