From: Aiden Leong <aiden.leong@aibsd.com>
To: masahiroy@kernel.org
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, ndesaulniers@google.com, nicolas@fjasle.eu
Subject: Re: [PATCH v2 2/4] modpost: inform compilers that fatal() never returns
Date: Mon, 22 Jan 2024 11:48:03 +0800 [thread overview]
Message-ID: <d9ac2960-6644-4a87-b5e4-4bfb6e0364a8@aibsd.com> (raw)
> The function fatal() never returns because modpost_log() calls exit(1)
> when LOG_FATAL is passed.
>
> Inform compilers of this fact so that unreachable code flow can be
> identified at compile time.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
>
> Changes in v2:
> - Use noreturn attribute together with alias
>
> scripts/mod/modpost.c | 3 +++
> scripts/mod/modpost.h | 5 ++++-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index ca0a90158f85..c13bc9095df3 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -90,6 +90,9 @@ void modpost_log(enum loglevel loglevel, const char
*fmt, ...)
> error_occurred = true;
> }
>
> +void __attribute__((alias("modpost_log")))
Hi Masahiro,
I cross-compile kernel on Apple Silicon MacBook Pro
and every thing works well until this patch.
My build command:
make ARCH=arm CROSS_COMPILE=arm-none-eabi- \
HOSTCFLAGS="-I/opt/homebrew/opt/openssl/include" \
HOSTLDFLAGS="-L/opt/homebrew/opt/openssl/lib"
Error message:
scripts/mod/modpost.c:93:21: error: aliases are not supported on darwin
Aiden Leong
> +modpost_log_noret(enum loglevel loglevel, const char *fmt, ...);
> +
> static inline bool strends(const char *str, const char *postfix)
> {
> if (strlen(str) < strlen(postfix))
> diff --git a/scripts/mod/modpost.h b/scripts/mod/modpost.h
> index 9fe974dc1a52..835cababf1b0 100644
> --- a/scripts/mod/modpost.h
> +++ b/scripts/mod/modpost.h
> @@ -200,6 +200,9 @@ enum loglevel {
> void __attribute__((format(printf, 2, 3)))
> modpost_log(enum loglevel loglevel, const char *fmt, ...);
>
> +void __attribute__((format(printf, 2, 3), noreturn))
> +modpost_log_noret(enum loglevel loglevel, const char *fmt, ...);
> +
> /*
> * warn - show the given message, then let modpost continue running,
still
> * allowing modpost to exit successfully. This should be used
when
> @@ -215,4 +218,4 @@ modpost_log(enum loglevel loglevel, const char
*fmt, ...);
> */
> #define warn(fmt, args...) modpost_log(LOG_WARN, fmt, ##args)
> #define error(fmt, args...) modpost_log(LOG_ERROR, fmt, ##args)
> -#define fatal(fmt, args...) modpost_log(LOG_FATAL, fmt, ##args)
> +#define fatal(fmt, args...) modpost_log_noret(LOG_FATAL, fmt, ##args)
> --
> 2.40.1
next reply other threads:[~2024-01-22 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 3:48 Aiden Leong [this message]
2024-01-22 13:29 ` Masahiro Yamada
2024-01-22 23:02 ` Nathan Chancellor
2024-01-27 13:41 ` Masahiro Yamada
-- strict thread matches above, loose matches on Subject: below --
2023-12-03 9:49 [PATCH v2 1/4] modpost: move __attribute__((format(printf, 2, 3))) to modpost.h Masahiro Yamada
2023-12-03 9:49 ` [PATCH v2 2/4] modpost: inform compilers that fatal() never returns Masahiro Yamada
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=d9ac2960-6644-4a87-b5e4-4bfb6e0364a8@aibsd.com \
--to=aiden.leong@aibsd.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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®