Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1584952
| From | Cong Wang <xiyou.wangcong@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: net: possible deadlock in skb_queue_tail |
| Date | 2017-02-21 00:00 +0100 |
| Message-ID | <td562-2h7-3@gated-at.bofh.it> (permalink) |
| References | <tcWm6-5gN-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Feb 20, 2017 at 5:29 AM, Andrey Konovalov <andreyknvl@google.com> wrote: > other info that might help us debug this: > > Possible unsafe locking scenario: > > CPU0 CPU1 > ---- ---- > lock(&(&pcpu->lock)->rlock); > lock(&(&list->lock)->rlock#3); > lock(&(&pcpu->lock)->rlock); > lock(&(&list->lock)->rlock#3); > They are different types of sockets and different lists of skb's, one is netlink socket the other is udp socket, so I don't think we could have a deadlock in this scenario, we probably need to explicitly mark them as different lockdep classes.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
net: possible deadlock in skb_queue_tail Andrey Konovalov <andreyknvl@google.com> - 2017-02-20 14:40 +0100 Re: net: possible deadlock in skb_queue_tail Cong Wang <xiyou.wangcong@gmail.com> - 2017-02-21 00:00 +0100 Re: net: possible deadlock in skb_queue_tail Florian Westphal <fw@strlen.de> - 2017-02-24 04:00 +0100
csiph-web