From: Daniel Borkmann <daniel@iogearbox.net>
To: hpa@linux.intel.com
Cc: linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>,
Pranith Kumar <bobby.prani@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
mancha security <mancha1@zoho.com>
Subject: [PATCH] compiler-intel: fix wrong compiler barrier() macro
Date: Wed, 29 Apr 2015 16:42:19 +0200 [thread overview]
Message-ID: <d6fd1f6fddaf1c42bccee403cb91bdea9eae908a.1430318087.git.daniel@iogearbox.net> (raw)
Cleanup commit 23ebdedc67e ("compiler-intel.h: Remove duplicate
definition") removed the double definition of __memory_barrier()
intrinsics.
However, in doing so, it also removed the preceding #undef barrier,
meaning, the actual barrier() macro from compiler-gcc.h with inline
asm is still in place when __GNUC__ is provided.
Subsequently, barrier() can never be defined as __memory_barrier()
from compiler.h since it already has a definition in place and if
we trust the comment in compiler-intel.h, ecc doesn't support gcc
specific asm statements. I don't have an ecc at hand, so a revert
of that cleanup would be the safest option, imho, as it has been
like this since pre-git times.
Fixes: 73679e508201 ("compiler-intel.h: Remove duplicate definition")
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Cc: Pranith Kumar <bobby.prani@gmail.com>
Cc: H. Peter Anvin <hpa@linux.intel.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: mancha security <mancha1@zoho.com>
---
include/linux/compiler-intel.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/compiler-intel.h b/include/linux/compiler-intel.h
index ba147a1..5529c52 100644
--- a/include/linux/compiler-intel.h
+++ b/include/linux/compiler-intel.h
@@ -13,9 +13,12 @@
/* Intel ECC compiler doesn't support gcc specific asm stmts.
* It uses intrinsics to do the equivalent things.
*/
+#undef barrier
#undef RELOC_HIDE
#undef OPTIMIZER_HIDE_VAR
+#define barrier() __memory_barrier()
+
#define RELOC_HIDE(ptr, off) \
({ unsigned long __ptr; \
__ptr = (unsigned long) (ptr); \
--
1.9.3
next reply other threads:[~2015-04-29 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 14:42 Daniel Borkmann [this message]
2015-04-29 14:51 ` Pranith Kumar
2015-04-29 14:59 ` mancha security
2015-04-29 16:40 ` Pranith Kumar
2015-04-29 16:59 ` Daniel Borkmann
2015-04-29 17:17 ` Pranith Kumar
2015-04-30 5:58 ` mancha security
2015-04-29 15:04 ` Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6fd1f6fddaf1c42bccee403cb91bdea9eae908a.1430318087.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=bobby.prani@gmail.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mancha1@zoho.com \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®