linux-kernel - Re: [GIT PULL] core/mutexes changes for v3.11: W/W mutex support

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: <20130705062345.GA29487@gmail.com>
Date:	Fri, 5 Jul 2013 08:23:45 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Maarten Lankhorst <maarten.lankhorst@...onical.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Airlie <airlied@...il.com>
Subject: Re: [GIT PULL] core/mutexes changes for v3.11: W/W mutex support


* Maarten Lankhorst <maarten.lankhorst@...onical.com> wrote:

> Hey,
> 
> Op 03-07-13 02:54, Linus Torvalds schreef:
> > On Mon, Jul 1, 2013 at 1:22 AM, Ingo Molnar <mingo@...nel.org> wrote:
> >> Please pull the latest core-mutexes-for-linus git tree from:
> >>
> >>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-mutexes-for-linus
> >>
> >>    HEAD: 166989e366ffa66108b2f37b870e66b85b2185ad locking-selftests: Handle unexpected failures more strictly
> >>
> >> This tree adds support for wound/wait style locks, which the graphics guys
> >> would like to make use of in the TTM graphics subsystem.
> > So I pulled this, but I'm not particularly happy with how this (very
> > unusual) lock pollutes <linux/mutex.h> that pretty much every single
> > file ends up including.
> >
> > So I'd really prefer to see the ww_mutex() support split up into
> > <linux/ww_mutex.h>, rather than making the compiler have to parse and
> > remember that stuff when 99.99% of all files do not care about it or
> > need it.
> 
> Sounds good to me, but can it wait until with the drm pull is done?

The ordering should not matter much as the combination will be tested in 
linux-next anyway.

> Preliminary diff below.

Looks good to me at first sight. Please send a tested, changelogged, 
signed off version.

Thanks,

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