From: Nick Desaulniers <ndesaulniers@google.com>
To: "Paul E . McKenney" <paulmck@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org,
clang-built-linux@googlegroups.com,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [PATCH v2] srcu: avoid escaped section names
Date: Tue, 29 Sep 2020 12:25:49 -0700 [thread overview]
Message-ID: <20200929192549.501516-1-ndesaulniers@google.com> (raw)
In-Reply-To: <CAKwvOd=s+N4+X94sTams_hKn8uV5Hc6QyCc7OHyOGC-JFesS8A@mail.gmail.com>
The stringification operator, `#`, in the preprocessor escapes strings.
For example, `# "foo"` becomes `"\"foo\""`. GCC and Clang differ in how
they treat section names that contain \".
The portable solution is to not use a string literal with the
preprocessor stringification operator.
Link: https://bugs.llvm.org/show_bug.cgi?id=42950
Fixes: commit fe15b50cdeee ("srcu: Allocate per-CPU data for DEFINE_SRCU() in modules")
Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
---
Changes V1->V2:
* drop unrelated Kconfig changes accidentally committed in v1.
include/linux/srcutree.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/srcutree.h b/include/linux/srcutree.h
index 9cfcc8a756ae..9de652f4e1bd 100644
--- a/include/linux/srcutree.h
+++ b/include/linux/srcutree.h
@@ -124,7 +124,7 @@ struct srcu_struct {
# define __DEFINE_SRCU(name, is_static) \
is_static struct srcu_struct name; \
struct srcu_struct * const __srcu_struct_##name \
- __section("___srcu_struct_ptrs") = &name
+ __section(___srcu_struct_ptrs) = &name
#else
# define __DEFINE_SRCU(name, is_static) \
static DEFINE_PER_CPU(struct srcu_data, name##_srcu_data); \
--
2.28.0.709.gb0816b6eb0-goog
next prev parent reply other threads:[~2020-09-29 19:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 19:22 [PATCH] srcu: avoid escaped section names Nick Desaulniers
2020-09-29 19:22 ` Nick Desaulniers
2020-09-29 19:25 ` Nick Desaulniers [this message]
2020-09-29 23:45 ` [PATCH v2] " Kees Cook
2020-09-30 16:27 ` Nathan Chancellor
2020-09-30 16:41 ` Sedat Dilek
2020-09-30 18:57 ` Joe Perches
2020-09-30 19:16 ` [RFC PATCH next-20200930] treewide: Convert macro and uses of __section(foo) to __section("foo") Joe Perches
2020-09-30 21:40 ` Nick Desaulniers
2020-09-30 22:06 ` Joe Perches
2020-09-30 22:12 ` Joe Perches
2020-09-30 22:20 ` Nick Desaulniers
2020-09-30 22:25 ` Joe Perches
2020-09-30 22:56 ` Joe Perches
2020-10-01 10:15 ` Miguel Ojeda
2020-10-01 19:05 ` Joe Perches
2020-10-01 19:39 ` Segher Boessenkool
2020-10-01 20:19 ` Joe Perches
2020-10-05 18:36 ` Nick Desaulniers
2020-10-05 18:46 ` Joe Perches
2020-10-06 0:34 ` Joel Stanley
2020-10-06 3:22 ` Joe Perches
2020-09-30 20:40 ` [PATCH v2] srcu: avoid escaped section names Paul E. McKenney
2020-09-30 20:55 ` Nick Desaulniers
2020-10-02 20:51 ` Paul E. McKenney
2020-10-05 18:29 ` Nick Desaulniers
2020-10-05 18:38 ` Sedat Dilek
2020-10-05 18:49 ` Paul E. McKenney
2020-10-06 6:56 ` Nathan Chancellor
2020-10-07 21:05 ` Paul E. McKenney
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=20200929192549.501516-1-ndesaulniers@google.com \
--to=ndesaulniers@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).