From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:49736 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726065AbeKRAgh (ORCPT ); Sat, 17 Nov 2018 19:36:37 -0500 Date: Sat, 17 Nov 2018 08:29:03 -0500 From: Sasha Levin To: Tom Zanussi Cc: Greg Kroah-Hartman , stable@vger.kernel.org Subject: Re: Request for 3.18-stable: a63b03e2d247 ("mutex: Always clear owner field upon mutex_unlock()") Message-ID: <20181117132903.GM1706@sasha-vm> References: <1542396159.7838.21.camel@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1542396159.7838.21.camel@kernel.org> Sender: stable-owner@vger.kernel.org List-ID: On Fri, Nov 16, 2018 at 01:22:39PM -0600, Tom Zanussi wrote: >Hi Greg, > >I noticed that 3.18.125 added commit bc07ee33284a ('Revert "drm/i915: >Fix mutex->owner inspection race under DEBUG_MUTEXES"'), which states >that the reason it can be applied is: > > The core fix was applied in > > commit a63b03e2d2477586440741677ecac45bcf28d7b1 > Author: Chris Wilson > Date: Tue Jan 6 10:29:35 2015 +0000 > > mutex: Always clear owner field upon mutex_unlock() > > (note the absence of stable@ tag) > > so we can now revert our band-aid commit 226e5ae9e5f910 for -next. > > >but that the commit referenced wasn't also pulled in. > >Please consider pulling that one too if you're going to do another 3.18 >stable release. Unless someone can ack that commit for stable (since it specifically states it shouldn't be included), I'd rather revert bc07ee33284a - it shouldn't have been merged in to begin with. -- Thanks, Sasha