From: Sasha Levin <sashal@kernel.org>
To: Tom Zanussi <zanussi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Re: Request for 3.18-stable: a63b03e2d247 ("mutex: Always clear owner field upon mutex_unlock()")
Date: Sat, 17 Nov 2018 08:29:03 -0500 [thread overview]
Message-ID: <20181117132903.GM1706@sasha-vm> (raw)
In-Reply-To: <1542396159.7838.21.camel@kernel.org>
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 <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.
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
next prev parent reply other threads:[~2018-11-18 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 19:22 Request for 3.18-stable: a63b03e2d247 ("mutex: Always clear owner field upon mutex_unlock()") Tom Zanussi
2018-11-17 13:29 ` Sasha Levin [this message]
2018-11-18 16:17 ` Tom Zanussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181117132903.GM1706@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=zanussi@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox