linux-kernel - Re: possible deadlock in proc_pid_attr

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]

Date:   Tue, 12 Dec 2017 14:00:05 -0800
From:   Eric Biggers <ebiggers3@...il.com>
To:     syzbot 
        <bot+d75766bf481d4fa47bb2e5a7073c9483fb0587cf@...kaller.appspotmail.com>
Cc:     adobriyan@...il.com, akinobu.mita@...il.com,
        akpm@...ux-foundation.org, dvyukov@...gle.com,
        ebiederm@...ssion.com, jpoimboe@...hat.com,
        linux-kernel@...r.kernel.org, mhocko@...e.com, mingo@...nel.org,
        syzkaller-bugs@...glegroups.com, vegard.nossum@...cle.com
Subject: Re: possible deadlock in proc_pid_attr_write

On Sat, Dec 09, 2017 at 02:43:00AM -0800, syzbot wrote:
> 
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, 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