linux-kernel - Re: kernel BUG at drivers/android/binder

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]

Date:   Fri, 17 May 2019 12:08:20 +0200
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     syzbot <syzbot+f9f3f388440283da2965@...kaller.appspotmail.com>
Cc:     Arve Hjønnevåg <arve@...roid.com>,
        Christian Brauner <christian@...uner.io>,
        "open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Joel Fernandes <joel@...lfernandes.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Martijn Coenen <maco@...roid.com>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        Todd Kjos <tkjos@...roid.com>, Todd Kjos <tkjos@...gle.com>
Subject: Re: kernel BUG at drivers/android/binder_alloc.c:LINE! (3)

On Fri, Mar 29, 2019 at 10:55 AM syzbot
<syzbot+f9f3f388440283da2965@...kaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+f9f3f388440283da2965@...kaller.appspotmail.com
>
> Tested on:
>
> commit:         8c2ffd91 Linux 5.1-rc2
> git tree:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git master
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8dcdce25ea72bedf
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> patch:          https://syzkaller.appspot.com/x/patch.diff?x=10fed663200000
>
> Note: testing is done by a robot and is best-effort only.


Todd,

Should this patch fix the bug? Should we close the bug as fixed then?
In my local testing I see this BUG still fires, but if we will leave
old fixed bugs open, we will not get notifications about new crashes.