mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vasily Averin <vvs@virtuozzo.com>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] notifiers: double register detection
Date: Thu, 27 Oct 2016 13:44:49 +0300	[thread overview]
Message-ID: <702f88ae-1610-48b8-7adf-b43cbfb7f6f9@virtuozzo.com> (raw)
In-Reply-To: <105a9bce-5539-73f1-2683-e52dba870c04@virtuozzo.com>

Dear Andrew,
could you please pick up this patch?

It helps to detect double register of the same notifiers.
This kind of problem can lead to unexpected failures (some notifiers can be not called),
endless cycles, memory corruption or crashes.
Initially I've found such cases in OpenVZ kernels in our custom code,
then found similar bug in mainline nfsd (commit 1eca45f8)

On 21.09.2016 15:33, Vasily Averin wrote:
> WARN_ON should help to detect double register of the same notifiers
> 
> Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
> ---
>  kernel/notifier.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/kernel/notifier.c b/kernel/notifier.c
> index fd2c9ac..e02b2f0 100644
> --- a/kernel/notifier.c
> +++ b/kernel/notifier.c
> @@ -22,6 +22,7 @@ static int notifier_chain_register(struct notifier_block **nl,
>  		struct notifier_block *n)
>  {
>  	while ((*nl) != NULL) {
> +		WARN_ON((*nl) == n);
>  		if (n->priority > (*nl)->priority)
>  			break;
>  		nl = &((*nl)->next);
> 

      reply	other threads:[~2016-10-27 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 12:33 Vasily Averin
2016-10-27 10:44 ` Vasily Averin [this message]

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=702f88ae-1610-48b8-7adf-b43cbfb7f6f9@virtuozzo.com \
    --to=vvs@virtuozzo.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.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®