linux-kernel - Re: [PATCH -tip/master 5/7] locking/mutex: Use MUTEX_SPIN_ON

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: <1406733596.3544.8.camel@j-VirtualBox>
Date:	Wed, 30 Jul 2014 08:19:56 -0700
From:	Jason Low <jason.low2@...com>
To:	Davidlohr Bueso <davidlohr@...com>
Cc:	peterz@...radead.org, mingo@...nel.org, aswin@...com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -tip/master 5/7] locking/mutex: Use MUTEX_SPIN_ON_OWNER
 when appropriate

On Sun, 2014-07-27 at 22:18 -0700, Davidlohr Bueso wrote:
> 4badad35 (locking/mutex: Disable optimistic spinning on some
> architectures) added a ARCH_SUPPORTS_ATOMIC_RMW flag to
> disable the mutex optimistic feature on specific archs.
> 
> Because CONFIG_MUTEX_SPIN_ON_OWNER only depended on DEBUG and
> SMP, it was ok to have the ->owner field conditional a bit
> flexible. However by adding a new variable to the matter,
> we can waste space with the unused field, ie: CONFIG_SMP &&
> (!CONFIG_MUTEX_SPIN_ON_OWNER && !CONFIG_DEBUG_MUTEX).
> 
> Signed-off-by: Davidlohr Bueso <davidlohr@...com>

Acked-by: Jason Low <jason.low2@...com>

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