mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-28 07:04:00 +08:00
9ab55d7f24
The C11 _Static_assert() keyword may be used at module scope, and we
need to teach genksyms about it to not abort with an error. We currently
have a growing number of static_assert() (but also direct usage of
_Static_assert()) users at module scope:
git grep -E '^_Static_assert\(|^static_assert\(' | grep -v '^tools' | wc -l
135
More recently, when enabling CONFIG_MODVERSIONS with CONFIG_KCSAN, we
observe a number of warnings:
WARNING: modpost: EXPORT symbol "<..all kcsan symbols..>" [vmlinux] [...]
When running a preprocessed source through 'genksyms -w' a number of
syntax errors point at usage of static_assert()s. In the case of
kernel/kcsan/encoding.h, new static_assert()s had been introduced which
used expressions that appear to cause genksyms to not even be able to
recover from the syntax error gracefully (as it appears was the case
previously).
Therefore, make genksyms ignore all _Static_assert() and the contained
expression. With the fix, usage of _Static_assert() no longer cause
"syntax error" all over the kernel, and the above modpost warnings for
KCSAN are gone, too.
Signed-off-by: Marco Elver <elver@google.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
79 lines
2.2 KiB
C
79 lines
2.2 KiB
C
// SPDX-License-Identifier: GPL-2.0-only
|
|
static struct resword {
|
|
const char *name;
|
|
int token;
|
|
} keywords[] = {
|
|
{ "__GENKSYMS_EXPORT_SYMBOL", EXPORT_SYMBOL_KEYW },
|
|
{ "__asm", ASM_KEYW },
|
|
{ "__asm__", ASM_KEYW },
|
|
{ "__attribute", ATTRIBUTE_KEYW },
|
|
{ "__attribute__", ATTRIBUTE_KEYW },
|
|
{ "__const", CONST_KEYW },
|
|
{ "__const__", CONST_KEYW },
|
|
{ "__extension__", EXTENSION_KEYW },
|
|
{ "__inline", INLINE_KEYW },
|
|
{ "__inline__", INLINE_KEYW },
|
|
{ "__signed", SIGNED_KEYW },
|
|
{ "__signed__", SIGNED_KEYW },
|
|
{ "__typeof", TYPEOF_KEYW },
|
|
{ "__typeof__", TYPEOF_KEYW },
|
|
{ "__volatile", VOLATILE_KEYW },
|
|
{ "__volatile__", VOLATILE_KEYW },
|
|
{ "__builtin_va_list", VA_LIST_KEYW },
|
|
|
|
{ "__int128", BUILTIN_INT_KEYW },
|
|
{ "__int128_t", BUILTIN_INT_KEYW },
|
|
{ "__uint128_t", BUILTIN_INT_KEYW },
|
|
|
|
// According to rth, c99 defines "_Bool", "__restrict", "__restrict__", "restrict". KAO
|
|
{ "_Bool", BOOL_KEYW },
|
|
{ "__restrict", RESTRICT_KEYW },
|
|
{ "__restrict__", RESTRICT_KEYW },
|
|
{ "restrict", RESTRICT_KEYW },
|
|
{ "asm", ASM_KEYW },
|
|
|
|
// c11 keywords that can be used at module scope
|
|
{ "_Static_assert", STATIC_ASSERT_KEYW },
|
|
|
|
// attribute commented out in modutils 2.4.2. People are using 'attribute' as a
|
|
// field name which breaks the genksyms parser. It is not a gcc keyword anyway.
|
|
// KAO. },
|
|
// { "attribute", ATTRIBUTE_KEYW },
|
|
|
|
{ "auto", AUTO_KEYW },
|
|
{ "char", CHAR_KEYW },
|
|
{ "const", CONST_KEYW },
|
|
{ "double", DOUBLE_KEYW },
|
|
{ "enum", ENUM_KEYW },
|
|
{ "extern", EXTERN_KEYW },
|
|
{ "float", FLOAT_KEYW },
|
|
{ "inline", INLINE_KEYW },
|
|
{ "int", INT_KEYW },
|
|
{ "long", LONG_KEYW },
|
|
{ "register", REGISTER_KEYW },
|
|
{ "short", SHORT_KEYW },
|
|
{ "signed", SIGNED_KEYW },
|
|
{ "static", STATIC_KEYW },
|
|
{ "struct", STRUCT_KEYW },
|
|
{ "typedef", TYPEDEF_KEYW },
|
|
{ "typeof", TYPEOF_KEYW },
|
|
{ "union", UNION_KEYW },
|
|
{ "unsigned", UNSIGNED_KEYW },
|
|
{ "void", VOID_KEYW },
|
|
{ "volatile", VOLATILE_KEYW },
|
|
};
|
|
|
|
#define NR_KEYWORDS (sizeof(keywords)/sizeof(struct resword))
|
|
|
|
static int is_reserved_word(register const char *str, register unsigned int len)
|
|
{
|
|
int i;
|
|
for (i = 0; i < NR_KEYWORDS; i++) {
|
|
struct resword *r = keywords + i;
|
|
int l = strlen(r->name);
|
|
if (len == l && !memcmp(str, r->name, len))
|
|
return r->token;
|
|
}
|
|
return -1;
|
|
}
|