From: Steven Rostedt <rostedt@goodmis.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, netdev@vger.kernel.org
Subject: Re: [RT PATCH 2/2] net: add a lock around icmp_sk()
Date: Wed, 31 Aug 2016 13:03:46 -0400 [thread overview]
Message-ID: <20160831130346.7c60c24b@gandalf.local.home> (raw)
In-Reply-To: <1472661463.14381.327.camel@edumazet-glaptop3.roam.corp.google.com>
On Wed, 31 Aug 2016 09:37:43 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2016-08-31 at 18:00 +0200, Sebastian Andrzej Siewior wrote:
> > It looks like the this_cpu_ptr() access in icmp_sk() is protected with
> > local_bh_disable(). To avoid missing serialization in -RT I am adding
> > here a local lock. No crash has been observed, this is just precaution.
> >
>
>
> Hmm...
>
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > ---
> > net/ipv4/icmp.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c
> > index c1f1d5030d37..63731fd6af3e 100644
> > --- a/net/ipv4/icmp.c
> > +++ b/net/ipv4/icmp.c
> > @@ -78,6 +78,7 @@
> > #include <linux/string.h>
> > #include <linux/netfilter_ipv4.h>
> > #include <linux/slab.h>
> > +#include <linux/locallock.h>
> > #include <net/snmp.h>
> > #include <net/ip.h>
> > #include <net/route.h>
> > @@ -205,6 +206,8 @@ static const struct icmp_control icmp_pointers[NR_ICMP_TYPES+1];
> > *
> > * On SMP we have one ICMP socket per-cpu.
> > */
> > +static DEFINE_LOCAL_IRQ_LOCK(icmp_sk_lock);
> > +
> > static struct sock *icmp_sk(struct net *net)
> > {
> > return *this_cpu_ptr(net->ipv4.icmp_sk);
> > @@ -216,12 +219,14 @@ static inline struct sock *icmp_xmit_lock(struct net *net)
> >
> > local_bh_disable();
> >
> > + local_lock(icmp_sk_lock);
>
> Deadlock alert ?
> Please read the comment few lines after, explaining why we have to use
> spin_trylock().
> Or maybe I should double check what is local_lock() in RT
And I don't know exactly what the deadlock scenario of the comment
below is. Is it racing with a softirq somehow?
Note, in RT softirqs can schedule out, and are preemptable. But I don't
know enough about this code to know if that is enough to not have a
deadlock here.
-- Steve
>
> > sk = icmp_sk(net);
> >
> > if (unlikely(!spin_trylock(&sk->sk_lock.slock))) {
>
> ...
> > /* This can happen if the output path signals a
> > * dst_link_failure() for an outgoing ICMP packet.
> > */
>
>
> > + local_unlock(icmp_sk_lock);
> > local_bh_enable();
> > return NULL;
>
next prev parent reply other threads:[~2016-08-31 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 16:00 [RT PATCH 1/2] net: add back the missing serialization in ip_send_unicast_reply() Sebastian Andrzej Siewior
2016-08-31 16:00 ` [RT PATCH 2/2] net: add a lock around icmp_sk() Sebastian Andrzej Siewior
2016-08-31 16:37 ` Eric Dumazet
2016-08-31 17:03 ` Steven Rostedt [this message]
2016-09-01 8:11 ` Sebastian Andrzej Siewior
2016-09-01 13:11 ` Eric Dumazet
2016-08-31 16:15 ` [RT PATCH 1/2] net: add back the missing serialization in ip_send_unicast_reply() Steven Rostedt
2016-08-31 16:36 ` Sebastian Andrzej Siewior
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=20160831130346.7c60c24b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).