linux-kernel - Re: possible deadlock in lock

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

Message-ID: <20171212215920.GH185376@gmail.com>
Date:   Tue, 12 Dec 2017 13:59:20 -0800
From:   Eric Biggers <ebiggers3@...il.com>
To:     syzbot 
        <bot+86a008206e8012f85c5feebf2873716e50f33fc4@...kaller.appspotmail.com>
Cc:     adobriyan@...il.com, akinobu.mita@...il.com,
        akpm@...ux-foundation.org, dvyukov@...gle.com,
        ebiederm@...ssion.com, jani.nikula@...el.com,
        linux-kernel@...r.kernel.org, mingo@...nel.org,
        syzkaller-bugs@...glegroups.com, vegard.nossum@...cle.com
Subject: Re: possible deadlock in lock_trace

On Thu, Nov 30, 2017 at 10:39:02AM -0800, syzbot wrote:
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@...glegroups.com.
> Please credit me with: Reported-by: syzbot <syzkaller@...glegroups.com>
> 
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new
> bug report.
> Note: all commands must start from beginning of the line in the email body.
> 

#syz dup: possible deadlock in seq_read