From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.kernel.org ([198.145.29.99]:33918 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1725729AbeKQFgU (ORCPT <rfc822;stable@vger.kernel.org>);
        Sat, 17 Nov 2018 00:36:20 -0500
Message-ID: <1542396159.7838.21.camel@kernel.org>
Subject: Request for 3.18-stable: a63b03e2d247 ("mutex: Always clear owner
 field upon mutex_unlock()")
From: Tom Zanussi <zanussi@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Date: Fri, 16 Nov 2018 13:22:39 -0600
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

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 <chris@chris-wilson.co.uk>
    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.

Thanks,

Tom