From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, Steven Rostedt <rostedt@goodmis.org>,
netdev@vger.kernel.org
Subject: Re: [RT PATCH 2/2] net: add a lock around icmp_sk()
Date: Thu, 1 Sep 2016 10:11:46 +0200 [thread overview]
Message-ID: <20160901081146.nabh52qssjkvztxz@linutronix.de> (raw)
In-Reply-To: <1472661463.14381.327.camel@edumazet-glaptop3.roam.corp.google.com>
On 2016-08-31 09:37:43 [-0700], Eric Dumazet wrote:
> > --- a/net/ipv4/icmp.c
> > +++ b/net/ipv4/icmp.c
> > @@ -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
On !RT local_lock() is preempt_disable().
On RT local_lock() is a per-CPU sleeping spinlock which can be taken
recursively by the owner.
On a "normal" ping reply we have
- icmp_reply()
- icmp_xmit_lock()
- local_lock()
- icmp_push_reply()
icmp_send()
- local_lock()
so that works. I didn't manage to resolve a possible dst_link_failure()
path but I would assume it is like the above (where the owner takes the
same local_lock() multiple times).
Sebastian
next prev parent reply other threads:[~2016-09-01 8:11 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
2016-09-01 8:11 ` Sebastian Andrzej Siewior [this message]
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=20160901081146.nabh52qssjkvztxz@linutronix.de \
--to=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=rostedt@goodmis.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).