linux-kernel - Re: [locking/ww_mutex] f2a5fec173 EIP: __mutex

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]

Date:   Tue, 28 Feb 2017 08:53:33 +0000
From:   Chris Wilson <chris@...is-wilson.co.uk>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     Nicolai Hähnle <Nicolai.Haehnle@....com>,
        "Peter Zijlstra (Intel)" <peterz@...radead.org>,
        Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
        LKP <lkp@...org>
Subject: Re: [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock

On Tue, Feb 28, 2017 at 11:59:24AM +0800, Fengguang Wu wrote:
> Hello,
> 
> Here is another bisect result with a different call trace.

Is this a single processor VM without pre-emption? It's a busy spin
loop, so relies on the other thread being run to break the loop. That
cpu_relax() should become cond_resched()?
-Chris


-- 
Chris Wilson, Intel Open Source Technology Centre