From: Jason Baron <jbaron@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] jump_label_inc may return before the code is patched
Date: Tue, 18 Oct 2011 16:54:41 -0400 [thread overview]
Message-ID: <20111018205441.GC2453@redhat.com> (raw)
In-Reply-To: <20111018175551.GH17571@redhat.com>
On Tue, Oct 18, 2011 at 07:55:51PM +0200, Gleb Natapov wrote:
> If cpu A calls jump_label_inc() just after atomic_add_return() is
> called by cpu B, atomic_inc_not_zero() will return value greater then
> zero and jump_label_inc() will return to a caller before jump_label_update()
> finishes its job on cpu B.
>
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> diff --git a/kernel/jump_label.c b/kernel/jump_label.c
> index a8ce450..e6f1f24 100644
> --- a/kernel/jump_label.c
> +++ b/kernel/jump_label.c
> @@ -66,8 +66,9 @@ void jump_label_inc(struct jump_label_key *key)
> return;
>
> jump_label_lock();
> - if (atomic_add_return(1, &key->enabled) == 1)
> + if (atomic_read(&key->enabled) == 0)
> jump_label_update(key, JUMP_LABEL_ENABLE);
> + atomic_inc(&key->enabled);
> jump_label_unlock();
> }
>
agreed, we shouldn't return before the update happens...did this cause any
actual problem in practice? Or just observed from code inspection?
Acked-by: Jason Baron <jbaron@redhat.com>
Thanks,
-Jason
next prev parent reply other threads:[~2011-10-18 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 17:55 [PATCH] jump_label_inc may return before the code is patched Gleb Natapov
2011-10-18 20:54 ` Jason Baron [this message]
2011-10-19 7:03 ` Gleb Natapov
2011-10-18 21:06 ` Steven Rostedt
2011-11-02 15:21 ` Gleb Natapov
2011-11-02 15:42 ` Steven Rostedt
2011-11-18 23:12 ` [tip:perf/core] jump_label: " tip-bot for Gleb Natapov
2011-12-06 6:27 ` tip-bot for Gleb Natapov
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=20111018205441.GC2453@redhat.com \
--to=jbaron@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).