netdev - Re: [PATCH net] 6pack,mkiss: fix possible deadlock

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] [day] [month] [year] [list]

Message-ID: <20191213215656.716e38be@cakuba.netronome.com>
Date:   Fri, 13 Dec 2019 21:56:56 -0800
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Eric Dumazet <edumazet@...gle.com>
Cc:     "David S . Miller" <davem@...emloft.net>,
        netdev <netdev@...r.kernel.org>,
        Eric Dumazet <eric.dumazet@...il.com>,
        syzbot <syzkaller@...glegroups.com>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH net] 6pack,mkiss: fix possible deadlock

On Thu, 12 Dec 2019 10:32:13 -0800, Eric Dumazet wrote:
> We got another syzbot report [1] that tells us we must use
> write_lock_irq()/write_unlock_irq() to avoid possible deadlock.

[...]

> Fixes: 6e4e2f811bad ("6pack,mkiss: fix lock inconsistency")

Looks like the commit in question got backported into same 2.6.x 
era stables so I added this one to stable/all queue.

> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
> Reported-by: syzbot <syzkaller@...glegroups.com>
> Cc: Arnd Bergmann <arnd@...db.de>

Applied, thank you!