From: Steven Rostedt <rostedt@goodmis.org>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jason Baron <jbaron@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
x86@kernel.org
Subject: Re: [PATCH net-next v2 3/8] x86/jump_label: expect default_nop if static_key gets enabled on boot-up
Date: Sat, 5 Oct 2013 20:05:58 -0400 [thread overview]
Message-ID: <20131005200558.3be2f841@gandalf.local.home> (raw)
In-Reply-To: <1381015258-7667-4-git-send-email-hannes@stressinduktion.org>
On Sun, 6 Oct 2013 01:20:53 +0200
Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
> net_get_random_once(intrduced in the next patch) uses static_keys in
> a way that they get enabled on boot-up instead of replaced with an
> ideal_nop. So check for default_nop on initial enabling.
>
> Other architectures don't check for this.
But they should.
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Jason Baron <jbaron@redhat.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: x86@kernel.org
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
> ---
> arch/x86/kernel/jump_label.c | 25 ++++++++++++++++++-------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/kernel/jump_label.c b/arch/x86/kernel/jump_label.c
> index ee11b7d..26d5a55 100644
> --- a/arch/x86/kernel/jump_label.c
> +++ b/arch/x86/kernel/jump_label.c
> @@ -42,15 +42,27 @@ static void __jump_label_transform(struct jump_entry *entry,
> int init)
> {
> union jump_code_union code;
> + const unsigned char default_nop[] = { STATIC_KEY_INIT_NOP };
> const unsigned char *ideal_nop = ideal_nops[NOP_ATOMIC5];
>
> if (type == JUMP_LABEL_ENABLE) {
> - /*
> - * We are enabling this jump label. If it is not a nop
> - * then something must have gone wrong.
> - */
> - if (unlikely(memcmp((void *)entry->code, ideal_nop, 5) != 0))
> - bug_at((void *)entry->code, __LINE__);
> + if (init) {
> + /*
> + * Jump label is enabled for the first time.
> + * So we expect a default_nop...
> + */
> + if (unlikely(memcmp((void *)entry->code, default_nop, 5)
> + != 0))
> + bug_at((void *)entry->code, __LINE__);
> + } else {
> + /*
> + * ...otherwise expect an ideal_nop. Otherwise
> + * something went horribly wrong.
> + */
> + if (unlikely(memcmp((void *)entry->code, ideal_nop, 5)
> + != 0))
> + bug_at((void *)entry->code, __LINE__);
> + }
I don't know if I like this change. This is similar to a bug we had
with the Xen folks, where they didn't realize that jump labels are not
suppose to be used (or set) before jump_label_init() is called.
I'll have to take a deeper look at this on Monday.
-- Steve
>
> code.jump = 0xe9;
> code.offset = entry->target -
> @@ -63,7 +75,6 @@ static void __jump_label_transform(struct jump_entry *entry,
> * are converting the default nop to the ideal nop.
> */
> if (init) {
> - const unsigned char default_nop[] = { STATIC_KEY_INIT_NOP };
> if (unlikely(memcmp((void *)entry->code, default_nop, 5) != 0))
> bug_at((void *)entry->code, __LINE__);
> } else {
next prev parent reply other threads:[~2013-10-06 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 23:20 Introduce support to lazy initialize mostly static keys v2 Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 1/8] ipv4: split inet_ehashfn to hash functions per compilation unit Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 2/8] ipv6: split inet6_ehashfn " Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 3/8] x86/jump_label: expect default_nop if static_key gets enabled on boot-up Hannes Frederic Sowa
2013-10-06 0:05 ` Steven Rostedt [this message]
2013-10-06 0:12 ` Hannes Frederic Sowa
2013-10-06 18:29 ` [PATCH] static_key: WARN on usage before jump_label_init was called Hannes Frederic Sowa
2013-10-07 15:51 ` Steven Rostedt
2013-10-07 16:57 ` [PATCH v2] " Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 4/8] net: introduce new macro net_get_random_once Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 5/8] inet: split syncookie keys for ipv4 and ipv6 and initialize with net_get_random_once Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 6/8] inet: convert inet_ehash_secret and ipv6_hash_secret to net_get_random_once Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 7/8] tcp: switch tcp_fastopen key generation " Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 8/8] net: switch net_secret " Hannes Frederic Sowa
2013-10-06 2:55 ` Introduce support to lazy initialize mostly static keys v2 David Miller
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=20131005200558.3be2f841@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hannes@stressinduktion.org \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).