mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Jason Baron <jbaron@akamai.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH mptcp-next] static_call: fix unused variable warn w/o MODULE
Date: Fri, 26 Mar 2021 12:12:35 +0100	[thread overview]
Message-ID: <YF3Bo8xfVt5UvGAg@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210326105023.2058860-1-matthieu.baerts@tessares.net>

On Fri, Mar 26, 2021 at 11:50:23AM +0100, Matthieu Baerts wrote:
> Here is the warning converted as error and reported by GCC:
> 
>   kernel/static_call.c: In function ‘__static_call_update’:
>   kernel/static_call.c:153:18: error: unused variable ‘mod’ [-Werror=unused-variable]
>     153 |   struct module *mod = site_mod->mod;
>         |                  ^~~
>   cc1: all warnings being treated as errors
>   make[1]: *** [scripts/Makefile.build:271: kernel/static_call.o] Error 1
> 
> This is simply because since recently, we no longer use 'mod' variable
> elsewhere if MODULE is unset.
> 
> When using 'make tinyconfig' to generate the default kconfig, MODULE is
> unset.
> 
> There are different ways to fix this warning. Here I tried to minimised
> the number of modified lines and not add more #ifdef. We could also move
> the declaration of the 'mod' variable inside the if-statement or
> directly use site_mod->mod.
> 
> Fixes: 698bacefe993 ("static_call: Align static_call_is_init() patching condition")
> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> ---
> 
> Notes:
>     Feel free to modify this patch directly if you prefer. I can of course
>     send a new version if needed.

Ah, I had indeed meant to take a look at this, but hadn't come around to
it. I think this is as nice a solution as there is, so let me go apply
this.

>  kernel/static_call.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/static_call.c b/kernel/static_call.c
> index 2c5950b0b90e..723fcc9d20db 100644
> --- a/kernel/static_call.c
> +++ b/kernel/static_call.c
> @@ -165,13 +165,13 @@ void __static_call_update(struct static_call_key *key, void *tramp, void *func)
>  
>  		stop = __stop_static_call_sites;
>  
> -#ifdef CONFIG_MODULES
>  		if (mod) {
> +#ifdef CONFIG_MODULES
>  			stop = mod->static_call_sites +
>  			       mod->num_static_call_sites;
>  			init = mod->state == MODULE_STATE_COMING;
> -		}
>  #endif
> +		}
>  


  reply	other threads:[~2021-03-26 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 10:50 Matthieu Baerts
2021-03-26 11:12 ` Peter Zijlstra [this message]
2021-04-09 11:30 ` [tip: locking/core] static_call: Fix " tip-bot2 for Matthieu Baerts

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=YF3Bo8xfVt5UvGAg@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=ardb@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=jbaron@akamai.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthieu.baerts@tessares.net \
    --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

all inboxes | Powered by JetHome®