linux-kernel - Re: [PATCH] mutex: Always clear owner field upon 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]

Message-ID: <1420562614.24290.5.camel@stgolabs.net>
Date:	Tue, 06 Jan 2015 08:43:34 -0800
From:	Davidlohr Bueso <dave@...olabs.net>
To:	Chris Wilson <chris@...is-wilson.co.uk>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [PATCH] mutex: Always clear owner field upon mutex_unlock()

On Tue, 2015-01-06 at 10:29 +0000, Chris Wilson wrote:
> Currently if DEBUG_MUTEXES is enabled, the mutex->owner field is only
> cleared iff debug_locks is active. This exposes a race to other users of
> the field where the mutex->owner may be still set to a stale value,
> potentially upsetting mutex_spin_on_owner() among others.
> 
> References: https://bugs.freedesktop.org/show_bug.cgi?id=87955
> Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Daniel Vetter <daniel.vetter@...ll.ch>

Acked-by: Davidlohr Bueso <dave@...olabs.net>

--
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/