Re: possible deadlock in xfrm_policy_delete

2020-09-24 Thread Herbert Xu
On Thu, Sep 24, 2020 at 09:30:03AM +0200, pet...@infradead.org wrote: > On Thu, Sep 24, 2020 at 06:44:12AM +0200, Dmitry Vyukov wrote: > > On Thu, Sep 24, 2020 at 6:36 AM Herbert Xu > > wrote: > > > > (k-slock-AF_INET6){+.-.}-{2:2} > > That's a seqlock. Are you sure? Line 2503 in net/ipv4/tcp.

Re: possible deadlock in xfrm_policy_delete

2020-09-24 Thread peterz
On Thu, Sep 24, 2020 at 06:44:12AM +0200, Dmitry Vyukov wrote: > On Thu, Sep 24, 2020 at 6:36 AM Herbert Xu > wrote: > > > (k-slock-AF_INET6){+.-.}-{2:2} That's a seqlock. > > What's going on with all these bogus lockdep reports? > > > > These are two completely different locks, one is for TCP

Re: possible deadlock in xfrm_policy_delete

2020-09-23 Thread Herbert Xu
On Thu, Sep 24, 2020 at 06:44:12AM +0200, Dmitry Vyukov wrote: > > FWIW one of the dups of this issue was bisected to: > > commit 1909760f5fc3f123e47b4e24e0ccdc0fc8f3f106 > Author: Ahmed S. Darwish > Date: Fri Sep 4 15:32:31 2020 + > > seqlock: PREEMPT_RT: Do not starve seqlock_t write

Re: possible deadlock in xfrm_policy_delete

2020-09-23 Thread Herbert Xu
On Sun, Sep 20, 2020 at 01:22:14PM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit:5fa35f24 Add linux-next specific files for 20200916 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=1122e2d990 > kernel config

possible deadlock in xfrm_policy_delete

2020-09-20 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:5fa35f24 Add linux-next specific files for 20200916 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1122e2d990 kernel config: https://syzkaller.appspot.com/x/.config?x=6bdb7e39caf48f53 dashboard