linux-kernel - Re: Kernel 4.17.4 lockup

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]

Message-ID: <2022d212-62f2-a163-2493-abecfbafa07b@intel.com>
Date:   Wed, 11 Jul 2018 09:24:20 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     "H.J. Lu" <hjl.tools@...il.com>
Cc:     "H. Peter Anvin" <hpa@...or.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Mel Gorman <mgorman@...e.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Rik van Riel <riel@...riel.com>,
        Minchan Kim <minchan@...nel.org>
Subject: Re: Kernel 4.17.4 lockup

On 07/11/2018 08:40 AM, H.J. Lu wrote:
> This is a quad-core machine with HT and 6 GB RAM.  The workload is
> x32 GCC build and test with "make -j8".  The bug is triggered during GCC
> test after a couple hours.  I have a script to set up my workload:
> 
> https://github.com/hjl-tools/gcc-regression
> 
> with a cron job
> 
> # It takes about 3 hour to bootstrap x86-64 GCC and 3 hour to run tests,
> TIMEOUT=480
> # Run it every hour,
> 30 * * * * /export/gnu/import/git/gcc-test-x32/gcc-build -mx32
> --with-pic > /dev/null 2>&1

Oh, fun, one of those.

How long does it take to reproduce?