linux-kernel - [tip:x86/vdso] x86, vdso: Add a lot more dummy locking functions to vclock

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:	Sun, 16 Feb 2014 16:54:10 -0800
From:	"tip-bot for H. Peter Anvin" <tipbot@...or.com>
To:	linux-tip-commits@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
	stefani@...bold.net, tglx@...utronix.de, hpa@...ux.intel.com
Subject: [tip:x86/vdso] x86, vdso:
  Add a lot more dummy locking functions to vclock_gettime.c

Commit-ID:  4b5e4f908855a66f0957bf35137ce3ee37c05230
Gitweb:     http://git.kernel.org/tip/4b5e4f908855a66f0957bf35137ce3ee37c05230
Author:     H. Peter Anvin <hpa@...ux.intel.com>
AuthorDate: Sun, 16 Feb 2014 16:44:25 -0800
Committer:  H. Peter Anvin <hpa@...ux.intel.com>
CommitDate: Sun, 16 Feb 2014 16:44:25 -0800

x86, vdso: Add a lot more dummy locking functions to vclock_gettime.c

We need a lot more dummy locking functions to build in all possible
configurations.

Cc: Stefani Seibold <stefani@...bold.net>
Link: http://lkml.kernel.org/r/1392587568-7325-10-git-send-email-stefani@seibold.net
Signed-off-by: H. Peter Anvin <hpa@...ux.intel.com>
---
 arch/x86/vdso/vdso32/vclock_gettime.c | 58 +++++++++++++++++++++++++++++++++--
 1 file changed, 55 insertions(+), 3 deletions(-)

diff --git a/arch/x86/vdso/vdso32/vclock_gettime.c b/arch/x86/vdso/vdso32/vclock_gettime.c
index 5de5057..56465ad 100644
--- a/arch/x86/vdso/vdso32/vclock_gettime.c
+++ b/arch/x86/vdso/vdso32/vclock_gettime.c
@@ -40,17 +40,69 @@
 #define _ASM_X86_SPINLOCK_H
 
 /*
- * dummys for unneeded arck_spin functions
+ * dummys for unneeded arch_spin functions
  */
-static inline void arch_spin_unlock_wait(void *p)
+static inline void arch_spin_lock(void *lock)
 {
 }
 
-static inline int arch_spin_is_locked(void *p)
+static inline int arch_spin_trylock(void *lock)
 {
 	return 0;
 }
 
+static inline void arch_spin_unlock(void *lock)
+{
+}
+
+static inline void arch_spin_lock_flags(void *lock,
+					unsigned long flags)
+{
+}
+
+static inline void arch_spin_unlock_wait(void *lock)
+{
+}
+
+static inline int arch_spin_is_locked(void *lock)
+{
+	return 0;
+}
+
+static inline int arch_read_trylock(void *lock)
+{
+	return 0;
+}
+
+static inline int arch_write_trylock(void *lock)
+{
+	return 0;
+}
+
+static inline void arch_read_lock(void *rw)
+{
+}
+
+static inline void arch_write_lock(void *rw)
+{
+}
+
+static inline void arch_read_lock_flags(void *rw, unsigned long flags)
+{
+}
+
+static inline void arch_write_lock_flags(void *rw, unsigned long flags)
+{
+}
+
+static inline void arch_read_unlock(void *rw)
+{
+}
+
+static inline void arch_write_unlock(void *rw)
+{
+}
+
 /*
  * The define of CONFIG_ILLEGAL_POINTER_VALUE is also to prevent the
  * "warning: integer constant is too large..."
--
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/