From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 2/3] jump_labels: do not use unserialized static_key_enabled
Date: Wed, 2 Aug 2017 01:45:16 -0400 (EDT) [thread overview]
Message-ID: <1879111268.746025.1501652716698.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1501620734.25002.10.camel@edumazet-glaptop3.roam.corp.google.com>
----- Original Message -----
> From: "Eric Dumazet" <eric.dumazet@gmail.com>
> To: "Paolo Bonzini" <pbonzini@redhat.com>
> Cc: linux-kernel@vger.kernel.org, "Peter Zijlstra" <peterz@infradead.org>
> Sent: Tuesday, August 1, 2017 10:52:14 PM
> Subject: Re: [PATCH 2/3] jump_labels: do not use unserialized static_key_enabled
>
> On Tue, 2017-08-01 at 17:24 +0200, Paolo Bonzini wrote:
> > Any use of key->enabled (that is static_key_enabled and static_key_count)
> > outside jump_label_lock should handle its own serialization. The only
> > two that are not doing so are the UDP encapsulation static keys. Change
> > them to use static_key_enable, which now correctly tests key->enabled under
> > the jump label lock.
> >
> > diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
> > index 1d6219bf2d6b..74b7810df9fc 100644
> > --- a/net/ipv4/udp.c
> > +++ b/net/ipv4/udp.c
> > @@ -1644,8 +1644,7 @@ static int __udp_queue_rcv_skb(struct sock *sk,
> > struct sk_buff *skb)
> > static struct static_key udp_encap_needed __read_mostly;
> > void udp_encap_enable(void)
> > {
> > - if (!static_key_enabled(&udp_encap_needed))
> > - static_key_slow_inc(&udp_encap_needed);
> > + static_key_enable(&udp_encap_needed);
> > }
>
> Looks good to me, but static_key_enable() is not serialized either ?
>
> I suspect you should have CCed me on patch 1/3 :)
Yes, indeed... That's the "now correctly test" in the commit message.
What a difference one word makes. :)
You can find 1/3 at https://patchwork.kernel.org/patch/9874845/.
Paolo
next prev parent reply other threads:[~2017-08-02 5:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 15:24 [PATCH 0/3] jump_labels: concurrency fixes Paolo Bonzini
2017-08-01 15:24 ` [PATCH 1/3] jump_labels: fix concurrent static_key_enable/disable() Paolo Bonzini
2017-08-01 16:45 ` Peter Zijlstra
2017-08-01 16:46 ` Paolo Bonzini
2017-08-10 12:12 ` [tip:locking/core] jump_label: Fix " tip-bot for Paolo Bonzini
2017-08-01 15:24 ` [PATCH 2/3] jump_labels: do not use unserialized static_key_enabled Paolo Bonzini
2017-08-01 20:52 ` Eric Dumazet
2017-08-02 5:45 ` Paolo Bonzini [this message]
2017-08-10 12:12 ` [tip:locking/core] jump_label: Do not use unserialized static_key_enabled() tip-bot for Paolo Bonzini
2017-08-01 15:24 ` [PATCH 3/3] cpuset: make nr_cpusets private Paolo Bonzini
2017-08-02 1:08 ` Zefan Li
2017-08-10 12:13 ` [tip:locking/core] cpuset: Make " tip-bot for Paolo Bonzini
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=1879111268.746025.1501652716698.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
Powered by JetHome