linux-kernel - Re: Reminder: 5 open syzbot bugs in lockdep subsystem

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

Message-ID: <f614ac47-34c3-fac4-c096-fd835ce6d35a@acm.org>
Date:   Wed, 10 Jul 2019 07:14:10 -0700
From:   Bart Van Assche <bvanassche@....org>
To:     linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
        syzkaller-bugs@...glegroups.com, jeffv@...gle.com
Subject: Re: Reminder: 5 open syzbot bugs in lockdep subsystem

On 7/9/19 10:58 PM, Eric Biggers wrote:
> [This email was generated by a script.  Let me know if you have any suggestions
> to make it better, or if you want it re-generated with the latest status.]
> 
> Of the currently open syzbot reports against the upstream kernel, I've manually
> marked 5 of them as possibly being bugs in the lockdep subsystem.  I've listed
> these reports below, sorted by an algorithm that tries to list first the reports
> most likely to be still valid, important, and actionable.
> 
> Of these 5 bugs, 3 were seen in mainline in the last week.
> 
> Of these 5 bugs, 1 was bisected to a commit from the following person:
> 
> 	Bart Van Assche <bvanassche@....org>

(+jeffv)

Hi Eric,

Several days ago I had already explained to you that the bisection 
result that led to one of my commits did not make any sense to me. So I 
do not appreciate this kind of fingerpointing. Please stop doing this.

Bart.