Message-ID: <1419790377.8667.6.camel@stgolabs.net>
Subject: Re: [PATCH 2/8] locking/mutex: Get rid of use_ww_cxt param in
 common paths
From: Davidlohr Bueso <dave@stgolabs.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
        "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
        linux-kernel@vger.kernel.org
Date: Sun, 28 Dec 2014 10:12:57 -0800
In-Reply-To: <20141228162303.GA12952@dyad.arnhem.chello.nl>
References: <1419757883-4423-1-git-send-email-dave@stgolabs.net>
	 <1419757883-4423-3-git-send-email-dave@stgolabs.net>
	 <20141228162303.GA12952@dyad.arnhem.chello.nl>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org

On Sun, 2014-12-28 at 17:23 +0100, Peter Zijlstra wrote:
> On Sun, Dec 28, 2014 at 01:11:17AM -0800, Davidlohr Bueso wrote:
> > ... and simplify a bit the parameters of __mutex_lock_common(). This
> > is straightforward as we can just check if the ww cxt for NULL if passed
> > from non wait/wound paths.
> 
> 
> The reason for this trainwreck is because of some older GCC not actually doing
> the const propagation of the MULL pointer right.

That's a shame, I really detest all this ww mess.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/