possible deadlock in skb_queue_tail (2)

2021-02-16 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:dcc0b490 Merge tag 'powerpc-5.11-8' of git://git.kernel.or.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11a2fe9cd0 kernel config: https://syzkaller.appspot.com/x/.config?x=8cb23303ddb9411f das

Re: possible deadlock in skb_queue_tail

2018-04-04 Thread Dmitry Vyukov
On Wed, Apr 4, 2018 at 7:08 AM, Cong Wang wrote: > On Tue, Apr 3, 2018 at 4:42 AM, Kirill Tkhai wrote: >> On 03.04.2018 14:25, Dmitry Vyukov wrote: >>> On Tue, Apr 3, 2018 at 11:50 AM, Kirill Tkhai wrote: sk_diag_dump_icons() dumps only sockets in TCP_LISTEN state. TCP_LISTEN state may

Re: possible deadlock in skb_queue_tail

2018-04-03 Thread Cong Wang
On Tue, Apr 3, 2018 at 4:42 AM, Kirill Tkhai wrote: > On 03.04.2018 14:25, Dmitry Vyukov wrote: >> On Tue, Apr 3, 2018 at 11:50 AM, Kirill Tkhai wrote: >>> sk_diag_dump_icons() dumps only sockets in TCP_LISTEN state. >>> TCP_LISTEN state may be assigned in only place in net/unix/af_unix.c: >>> it

Re: possible deadlock in skb_queue_tail

2018-04-03 Thread Kirill Tkhai
On 03.04.2018 14:25, Dmitry Vyukov wrote: > On Tue, Apr 3, 2018 at 11:50 AM, Kirill Tkhai wrote: >> On 02.04.2018 12:20, syzbot wrote: >>> Hello, >>> >>> syzbot hit the following crash on net-next commit >>> 06b19fe9a6df7aaa423cd8404ebe5ac9ec4b2960 (Sun Apr 1 03:37:33 2018 +) >>> Merge branch

Re: possible deadlock in skb_queue_tail

2018-04-03 Thread Dmitry Vyukov
On Tue, Apr 3, 2018 at 11:50 AM, Kirill Tkhai wrote: > On 02.04.2018 12:20, syzbot wrote: >> Hello, >> >> syzbot hit the following crash on net-next commit >> 06b19fe9a6df7aaa423cd8404ebe5ac9ec4b2960 (Sun Apr 1 03:37:33 2018 +) >> Merge branch 'chelsio-inline-tls' >> syzbot dashboard link: >>

Re: possible deadlock in skb_queue_tail

2018-04-03 Thread Kirill Tkhai
On 02.04.2018 12:20, syzbot wrote: > Hello, > > syzbot hit the following crash on net-next commit > 06b19fe9a6df7aaa423cd8404ebe5ac9ec4b2960 (Sun Apr 1 03:37:33 2018 +) > Merge branch 'chelsio-inline-tls' > syzbot dashboard link: > https://syzkaller.appspot.com/bug?extid=6b495100f17ca8554ab9

possible deadlock in skb_queue_tail

2018-04-02 Thread syzbot
Hello, syzbot hit the following crash on net-next commit 06b19fe9a6df7aaa423cd8404ebe5ac9ec4b2960 (Sun Apr 1 03:37:33 2018 +) Merge branch 'chelsio-inline-tls' syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=6b495100f17ca8554ab9 Unfortunately, I don't have any reproducer fo

Re: net: possible deadlock in skb_queue_tail

2017-05-04 Thread Paolo Abeni
On Thu, 2017-05-04 at 15:49 +0200, Andrey Konovalov wrote: > On Fri, Feb 24, 2017 at 3:56 AM, Florian Westphal wrote: > > Andrey Konovalov wrote: > > > > [ CC Paolo ] > > > > > I've got the following error report while fuzzing the kernel with > > > syzkaller. > > > > > > On commit c470abd4fde

Re: net: possible deadlock in skb_queue_tail

2017-05-04 Thread Andrey Konovalov
On Fri, Feb 24, 2017 at 3:56 AM, Florian Westphal wrote: > Andrey Konovalov wrote: > > [ CC Paolo ] > >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). >> >> Unfortunately I can't reproduce it. > > This

Re: net: possible deadlock in skb_queue_tail

2017-02-23 Thread Florian Westphal
Andrey Konovalov wrote: [ CC Paolo ] > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). > > Unfortunately I can't reproduce it. This needs NETLINK_BROADCAST_ERROR enabled on a netlink socket that then s

Re: net: possible deadlock in skb_queue_tail

2017-02-20 Thread Cong Wang
On Mon, Feb 20, 2017 at 5:29 AM, Andrey Konovalov wrote: > other info that might help us debug this: > > Possible unsafe locking scenario: > >CPU0CPU1 > > lock(&(&pcpu->lock)->rlock); >lock(&(&list->

net: possible deadlock in skb_queue_tail

2017-02-20 Thread Andrey Konovalov
Hi, I've got the following error report while fuzzing the kernel with syzkaller. On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). Unfortunately I can't reproduce it. == [ INFO: possible circular locking dependency detected ] 4.10.0-r