linux-kernel - Re: inconsistent lock state in ila_xlat_nl_cmd_add

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201229173730.65f74253@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Tue, 29 Dec 2020 17:37:30 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     syzbot <syzbot+eaaf6c4a6a8cb1869d86@...kaller.appspotmail.com>
Cc:     davem@...emloft.net, gregkh@...uxfoundation.org,
        keescook@...omium.org, ktkhai@...tuozzo.com, kuznet@....inr.ac.ru,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        pombredanne@...b.com, stephen@...workplumber.org,
        syzkaller-bugs@...glegroups.com, tom@...bertland.com,
        yoshfuji@...ux-ipv6.org
Subject: Re: inconsistent lock state in ila_xlat_nl_cmd_add_mapping

On Mon, 13 Aug 2018 21:40:03 -0700 syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    78cbac647e61 Merge branch 'ip-faster-in-order-IP-fragments'
> git tree:       net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14df4828400000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=9100338df26ab75
> dashboard link: https://syzkaller.appspot.com/bug?extid=eaaf6c4a6a8cb1869d86
> compiler:       gcc (GCC) 8.0.1 20180413 (experimental)
> syzkaller repro:https://syzkaller.appspot.com/x/repro.syz?x=13069ad2400000
> 
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+eaaf6c4a6a8cb1869d86@...kaller.appspotmail.com

#syz invalid

Hard to track down what fixed this, but the lockdep splat is mixing up
locks from two different hashtables, so there was never a real issue
here.