mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>,
	Valentin Schneider <valentin.schneider@arm.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2] notifier: Return an error when a callback has already been registered
Date: Thu, 23 Dec 2021 15:00:47 -0500	[thread overview]
Message-ID: <YcTVb4thNW4RmEHn@rowland.harvard.edu> (raw)
In-Reply-To: <YcSWNdUBS8A2ZB3s@zn.tnic>

On Thu, Dec 23, 2021 at 04:31:01PM +0100, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
> 
> Return -EEXIST when a notifier callback has already been registered on a
> notifier chain.
> 
> This should avoid any homegrown registration tracking at the callsite
> like
> 
>   https://lore.kernel.org/amd-gfx/20210512013058.6827-1-mukul.joshi@amd.com
> 
> for example.
> 
> This version is an alternative of
> 
>   https://lore.kernel.org/r/20211108101157.15189-1-bp@alien8.de
> 
> which needed to touch every caller not checking the registration
> routine's return value.
> 
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---

Acked-by: Alan Stern <stern@rowland.harvard.edu>

>  kernel/notifier.c | 15 ++++++++-------
>  1 file changed, 8 insertions(+), 7 deletions(-)
> 
> diff --git a/kernel/notifier.c b/kernel/notifier.c
> index b8251dc0bc0f..ba005ebf4730 100644
> --- a/kernel/notifier.c
> +++ b/kernel/notifier.c
> @@ -20,12 +20,13 @@ BLOCKING_NOTIFIER_HEAD(reboot_notifier_list);
>   */
>  
>  static int notifier_chain_register(struct notifier_block **nl,
> -		struct notifier_block *n)
> +				   struct notifier_block *n)
>  {
>  	while ((*nl) != NULL) {
>  		if (unlikely((*nl) == n)) {
> -			WARN(1, "double register detected");
> -			return 0;
> +			WARN(1, "notifier callback %ps already registered",
> +			     n->notifier_call);
> +			return -EEXIST;
>  		}
>  		if (n->priority > (*nl)->priority)
>  			break;
> @@ -134,7 +135,7 @@ static int notifier_call_chain_robust(struct notifier_block **nl,
>   *
>   *	Adds a notifier to an atomic notifier chain.
>   *
> - *	Currently always returns zero.
> + *	Returns 0 on success, %-EEXIST on error.
>   */
>  int atomic_notifier_chain_register(struct atomic_notifier_head *nh,
>  		struct notifier_block *n)
> @@ -216,7 +217,7 @@ NOKPROBE_SYMBOL(atomic_notifier_call_chain);
>   *	Adds a notifier to a blocking notifier chain.
>   *	Must be called in process context.
>   *
> - *	Currently always returns zero.
> + *	Returns 0 on success, %-EEXIST on error.
>   */
>  int blocking_notifier_chain_register(struct blocking_notifier_head *nh,
>  		struct notifier_block *n)
> @@ -335,7 +336,7 @@ EXPORT_SYMBOL_GPL(blocking_notifier_call_chain);
>   *	Adds a notifier to a raw notifier chain.
>   *	All locking must be provided by the caller.
>   *
> - *	Currently always returns zero.
> + *	Returns 0 on success, %-EEXIST on error.
>   */
>  int raw_notifier_chain_register(struct raw_notifier_head *nh,
>  		struct notifier_block *n)
> @@ -406,7 +407,7 @@ EXPORT_SYMBOL_GPL(raw_notifier_call_chain);
>   *	Adds a notifier to an SRCU notifier chain.
>   *	Must be called in process context.
>   *
> - *	Currently always returns zero.
> + *	Returns 0 on success, %-EEXIST on error.
>   */
>  int srcu_notifier_chain_register(struct srcu_notifier_head *nh,
>  		struct notifier_block *n)
> -- 
> 2.29.2
> 
> 
> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2021-12-23 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 13:36 [PATCH] " Borislav Petkov
2021-12-02 14:16 ` Sebastian Andrzej Siewior
2021-12-02 14:23   ` Borislav Petkov
2021-12-02 14:31     ` Sebastian Andrzej Siewior
2021-12-02 14:46       ` Borislav Petkov
2021-12-02 15:41 ` Alan Stern
2021-12-02 15:56   ` Borislav Petkov
2021-12-23 15:31 ` [PATCH -v2] " Borislav Petkov
2021-12-23 18:16   ` Sebastian Andrzej Siewior
2021-12-23 20:00   ` Alan Stern [this message]
2021-12-29  9:58   ` [tip: core/core] " tip-bot2 for Borislav Petkov

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=YcTVb4thNW4RmEHn@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rostedt@goodmis.org \
    --cc=valentin.schneider@arm.com \
    --cc=x86@kernel.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®