netdev - Re: [PATCH] can: j1939: prevent deadlock by changing j1939_socks

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 for Android: free password hash cracker in your pocket

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

Message-Id: <8A7EE4B2-4DCE-40FF-B971-F67F402872BB@yahoo.com>
Date: Thu, 6 Jul 2023 21:39:04 -0700
From: Astra Joan <astrajoan@...oo.com>
To: dvyukov@...gle.com
Cc: Astra Joan <astrajoan@...oo.com>,
 davem@...emloft.net,
 edumazet@...gle.com,
 ivan.orlov0322@...il.com,
 kernel@...gutronix.de,
 kuba@...nel.org,
 linux-can@...r.kernel.org,
 linux-kernel@...r.kernel.org,
 linux@...pel-privat.de,
 mkl@...gutronix.de,
 netdev@...r.kernel.org,
 o.rempel@...gutronix.de,
 pabeni@...hat.com,
 robin@...tonic.nl,
 skhan@...uxfoundation.org,
 socketcan@...tkopp.net,
 syzbot+1591462f226d9cbf0564@...kaller.appspotmail.com,
 syzkaller-bugs@...glegroups.com,
 syzkaller@...glegroups.com
Subject: Re: [PATCH] can: j1939: prevent deadlock by changing j1939_socks_lock
 to rwlock

Hi Dmitry,

Yes, I initially wanted to test my patch against this bug, but only
later realized there should be a reproducer in order to use syz test.

Also, I believe my local testing should suffice to show the patch's
ability to mitigate the deadlock bug. In particular, the attached error
log could be avoided if my patch was applied to the upstream. Could 
anyone in the mailing list review the patch given this context?

Best regards,
Ziqi

View attachment "decode_netdevice.txt" of type "text/plain" (162952 bytes)