linux-kernel - Re: WARNING in get_pi

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+ao9upkykqCQod4to_hEj_iFzLP8Nv4+SvOApYi8Sh2Ow@mail.gmail.com>
Date:   Tue, 7 Nov 2017 17:16:13 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     syzbot 
        <bot+2af19c9e1ffe4d4ee1d16c56ae7580feaee75765@...kaller.appspotmail.com>,
        dvhart@...radead.org, LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        syzkaller-bugs@...glegroups.com,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: WARNING in get_pi_state

On Tue, Oct 31, 2017 at 11:38 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Tue, Oct 31, 2017 at 11:31:34AM +0100, Peter Zijlstra wrote:
>
>> And of course, now it went *splat*, lemme continue staring..
>
> PEBKAC, turns out I was running the kernel without the patch in, and it
> only took 3100 seconds to trigger the splat..
>
> I am now actually running the kernel with the patch in, I'll leave the
> machine running it for a few hours.


Let's tell the bot about the fix, otherwise it will never report bugs
in get_pi_state again:

#syz fix: futex: Fix more put_pi_state() vs. exit_pi_state_list() races