Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: Nicolas Schier <nicolas.schier@linux.dev>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modpost: drop '*_probe' from section check whitelist
Date: Wed, 22 Oct 2025 22:39:55 +0200	[thread overview]
Message-ID: <20251022203955.GA3256590@ax162> (raw)
In-Reply-To: <20251020091613.22562-1-johan@kernel.org>

On Mon, Oct 20, 2025 at 11:16:13AM +0200, Johan Hovold wrote:
> Several symbol patterns used to be whitelisted to allow drivers to refer
> to functions annotated with __devinit and __devexit, which have since
> been removed.
> 
> Commit e1dc1bfe5b27 ("modpost: remove more symbol patterns from the
> section check whitelist") removed most of these patterns but left
> '*_probe' after a reported warning in an irqchip driver.
> 
> Turns out that was indeed an incorrect reference which has now been
> fixed by commit 9b685058ca93 ("irqchip/qcom-irq-combiner: Fix section
> mismatch").
> 
> A recently added clocksource driver also relies on this suffix to
> suppress another valid warning, and that is being fixed separately. [1]
> 
> Note that drivers with valid reasons for suppressing the warnings can
> use the __ref macros.
> 
> Link: https://lore.kernel.org/lkml/20251017054943.7195-1-johan@kernel.org/ [1]
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
> 
> As mentioned above there are still two drivers relying on the "_probe"
> pattern to suppress valid warnings so perhaps it's best to hold off on
> merging this until the corresponding fixes are in mainline (e.g. next
> cycle or so unless Thomas can fast-track them).

Yeah, if it were fast tracked as a fix for 6.18, we could either use
that tag as the base for kbuild-next (as we have not take any patches
for 6.19 yet) or if they are 6.19 material, Thomas could provide us with
a signed tag or stable shared branch so that we could take this for 6.19
and have a clean tree. Whatever works.

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

>  scripts/mod/modpost.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index 47c8aa2a6939..5c499dace0bb 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -953,7 +953,7 @@ static int secref_whitelist(const char *fromsec, const char *fromsym,
>  	/* symbols in data sections that may refer to any init/exit sections */
>  	if (match(fromsec, PATTERNS(DATA_SECTIONS)) &&
>  	    match(tosec, PATTERNS(ALL_INIT_SECTIONS, ALL_EXIT_SECTIONS)) &&
> -	    match(fromsym, PATTERNS("*_ops", "*_probe", "*_console")))
> +	    match(fromsym, PATTERNS("*_ops", "*_console")))
>  		return 0;
>  
>  	/* Check for pattern 3 */
> -- 
> 2.49.1
> 

  parent reply	other threads:[~2025-10-22 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20  9:16 [PATCH] modpost: drop '*_probe' from section check whitelist Johan Hovold
2025-10-21  0:20 ` kernel test robot
2025-10-22 20:39 ` Nathan Chancellor [this message]
2025-11-12 16:48   ` Johan Hovold
2025-11-14  4:16     ` Nathan Chancellor
2025-11-14  8:45       ` Johan Hovold
2025-12-16  1:11       ` Johan Hovold
2025-11-15 15:36 ` Thomas Gleixner
2025-12-16 13:13 ` Nathan Chancellor

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=20251022203955.GA3256590@ax162 \
    --to=nathan@kernel.org \
    --cc=johan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nicolas.schier@linux.dev \
    --cc=tglx@linutronix.de \
    /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