linux-kernel - [PATCH] x86, paravirt: Avoid unused by set variables in rdmsr

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:	Thu, 12 May 2011 14:08:03 -0300
From:	Lucas De Marchi <lucas.de.marchi@...il.com>
To:	Andi Kleen <andi@...stfloor.org>,
	Jeremy Fitzhardinge <jeremy@...source.com>,
	Chris Wright <chrisw@...s-sol.org>,
	Alok Kataria <akataria@...are.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Cc:	virtualization@...ts.linux-foundation.org,
	Lucas De Marchi <lucas.demarchi@...fusion.mobi>,
	linux-kernel@...r.kernel.org
Subject: [PATCH] x86, paravirt: Avoid unused by set variables in rdmsr

Just like 5f755293 (x86, gcc-4.6: Avoid unused by set variables in
rdmsr) this patch silences GCC warnings about "set but not used
variables" in paravirt.h.

Signed-off-by: Lucas De Marchi <lucas.demarchi@...fusion.mobi>
---
 arch/x86/include/asm/paravirt.h |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/include/asm/paravirt.h b/arch/x86/include/asm/paravirt.h
index ebbc4d8..1e02d57 100644
--- a/arch/x86/include/asm/paravirt.h
+++ b/arch/x86/include/asm/paravirt.h
@@ -147,8 +147,8 @@ static inline int paravirt_wrmsr_regs(u32 *regs)
 do {						\
 	int _err;				\
 	u64 _l = paravirt_read_msr(msr, &_err);	\
-	val1 = (u32)_l;				\
-	val2 = _l >> 32;			\
+	(void)((val1) = (u32)_l);		\
+	(void)((val2) = (u32)(_l >> 32));	\
 } while (0)
 
 #define wrmsr(msr, val1, val2)			\
-- 
1.7.5.1

--
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/