linux-kernel - Re: [tip:core/locking] x86, um: Add generic barrier.h

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: <20140128193057.GG11314@laptop.programming.kicks-ass.net>
Date:	Tue, 28 Jan 2014 20:30:57 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	mingo@...nel.org, hpa@...or.com, jdike@...toit.com,
	linux-kernel@...r.kernel.org, richard@....at, tglx@...utronix.de
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:core/locking] x86, um: Add generic barrier.h

On Tue, Jan 28, 2014 at 11:25:12AM -0800, tip-bot for Peter Zijlstra wrote:
> Commit-ID:  673c36745c9f3100672853840b27e27638435e74
> Gitweb:     http://git.kernel.org/tip/673c36745c9f3100672853840b27e27638435e74
> Author:     Peter Zijlstra <peterz@...radead.org>
> AuthorDate: Tue, 28 Jan 2014 15:12:36 +0100
> Committer:  Ingo Molnar <mingo@...nel.org>
> CommitDate: Tue, 28 Jan 2014 15:27:36 +0100
> 
> x86, um: Add generic barrier.h
> 
> It appears arch/um doesn't have any asm/barrier.h; cure this by
> including the generic one. Since UM is !SMP the defaults are good
> enough.
> 
> ( The motivation are the latest MCS locking patches which use generic
>   barriers. )
> 
> Signed-off-by: Peter Zijlstra <peterz@...radead.org>
> Cc: Jeff Dike <jdike@...toit.com>
> Cc: Richard Weinberger <richard@....at>

I just talked to rw on IRC and he pointed out that commit 9af2452
(already in Linus' tree) does the same.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/