linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CACT4Y+bGjJjmMNMQZEZFTh8UnyXNYSTy97SxtuKaJ96XkALkWw@mail.gmail.com>
Date:   Wed, 5 Jul 2023 06:50:43 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Oleksij Rempel <o.rempel@...gutronix.de>
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, pabeni@...hat.com,
        robin@...tonic.nl, skhan@...uxfoundation.org,
        socketcan@...tkopp.net,
        syzbot+1591462f226d9cbf0564@...kaller.appspotmail.com,
        syzkaller-bugs@...glegroups.com,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: [PATCH] can: j1939: prevent deadlock by changing j1939_socks_lock
 to rwlock

On Wed, 5 Jul 2023 at 06:40, Oleksij Rempel <o.rempel@...gutronix.de> wrote:
>
> On Tue, Jul 04, 2023 at 10:55:47AM -0700, Astra Joan wrote:
> > Hi Oleksij,
> >
> > Thank you for providing help with the bug fix! The patch was created
> > when I was working on another bug:
> >
> > https://syzkaller.appspot.com/bug?extid=881d65229ca4f9ae8c84
> >
> > But the patch was not a direct fix of the problem reported in the
> > unregister_netdevice function call. Instead, it suppresses potential
> > deadlock information to guarantee the real bug would show up. Since I
> > have verified that the patch resolved a deadlock situation involving
> > the exact same locks, I'm pretty confident it would be a proper fix for
> > the current bug in this thread.
> >
> > I'm not sure, though, about how I could instruct Syzbot to create a
> > reproducer to properly test this patch. Could you or anyone here help
> > me find the next step? Thank you so much!
>
> Sorry, I'm not syzbot expert. I hope someone else can help here.

+syzkaller mailing list

Hi Astra,

You mean you have a reproducer and you want syzbot to run it with your patch?
No such feature exists at the moment.

Presumably you already run it locally, so I am not sure syzbot can add
much value here.