From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] ipv6: frags: fix a lockdep false positive
Date: Wed, 18 Apr 2018 23:20:16 -0400 (EDT) [thread overview]
Message-ID: <20180418.232016.1910578116691581991.davem@davemloft.net> (raw)
In-Reply-To: <20180418011144.71697-1-edumazet@google.com>
From: Eric Dumazet <edumazet@google.com>
Date: Tue, 17 Apr 2018 18:11:44 -0700
> lockdep does not know that the locks used by IPv4 defrag
> and IPv6 reassembly units are of different classes.
>
> It complains because of following chains :
>
> 1) sch_direct_xmit() (lock txq->_xmit_lock)
> dev_hard_start_xmit()
> xmit_one()
> dev_queue_xmit_nit()
> packet_rcv_fanout()
> ip_check_defrag()
> ip_defrag()
> spin_lock() (lock frag queue spinlock)
>
> 2) ip6_input_finish()
> ipv6_frag_rcv() (lock frag queue spinlock)
> ip6_frag_queue()
> icmpv6_param_prob() (lock txq->_xmit_lock at some point)
>
> We could add lockdep annotations, but we also can make sure IPv6
> calls icmpv6_param_prob() only after the release of the frag queue spinlock,
> since this naturally makes frag queue spinlock a leaf in lock hierarchy.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> ---
> Note do David: I chose net-next because of recent changes in net-next,
> and because it is a false positive, but can respin for net tree
> if you prefer. Thanks !
Yeah I think net-next is fine for this.
Applied, thanks.
prev parent reply other threads:[~2018-04-19 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 1:11 [PATCH net-next] ipv6: frags: fix a lockdep false positive Eric Dumazet
2018-04-19 3:20 ` David Miller [this message]
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=20180418.232016.1910578116691581991.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.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