stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Ben Hutchings <ben@decadent.org.uk>,
	Ian Campbell <ian.campbell@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, <stable@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "David Vrabel" <david.vrabel@citrix.com>,
	xen-devel@lists.xensource.com,
	"osstest service owner" <osstest-admin@xenproject.org>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: [Xen-devel] [linux-3.14 bisection] complete test-amd64-i386-xl-qcow2
Date: Mon, 12 Oct 2015 11:11:10 +0100	[thread overview]
Message-ID: <561B873E.5040803@citrix.com> (raw)
In-Reply-To: <1444342480.2956.274.camel@decadent.org.uk>

On 08/10/15 23:14, Ben Hutchings wrote:
> On Wed, 2015-09-02 at 10:18 +0100, Ian Campbell wrote:
>> [resending to correct stable address, sorry folks]
>>
>> TL;DR: Any backport of 30b03d05e074 to earlier than commit 1401c00e59e
>> ("xen/gntdev: convert priv->lock to a mutex", which was added in v4.0)
>> needs $something doing to it, either s/mutex/spinlock/ or (more likely)
>> backporting of 1401c00e59e too.
>>
>> Looking at LTS:
>>
>> 3.18.y:> 	>   Backported both.
>> 3.16.y:> 	>   Has backported neither
>> 3.14.y:> 	> * Only backported 30b03d05e074
>> 3.12.y:> 	>   Has backported neither
>> 3.10.y:> 	> * Only backported 30b03d05e074
>> 3.4.y:> 	>   Has backported neither
>> 3.2.y:> 	>   Has backported neither
>>
>> So AFAICT 3.14.y and 3.10.y need fixes, probably following 3.18 and
>> backporting 1401c00e59e.
>>
>> 3.16/12/4/2 might need to be careful if they subsequently pick up 30b03d05.
> [...]
> 
> I came up with the patch below for 3.2.  Let me know if it's not
> correct.

Please just take commit 1401c00e59e instead.

David

  parent reply	other threads:[~2015-10-12 10:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ZUgtn-0001q8-QQ@osstest.test-lab.xenproject.org>
     [not found] ` <1441099198.27618.13.camel@citrix.com>
     [not found]   ` <21989.30329.419566.715627@mariner.uk.xensource.com>
     [not found]     ` <1441101938.27618.17.camel@citrix.com>
2015-09-02  9:18       ` [linux-3.14 bisection] complete test-amd64-i386-xl-qcow2 Ian Campbell
2015-09-03 11:05         ` Luis Henriques
2015-09-03 11:16           ` [Xen-devel] " David Vrabel
2015-09-03 12:21             ` Luis Henriques
2015-09-11 15:10         ` Ian Campbell
2015-09-11 15:51           ` Greg Kroah-Hartman
2015-09-11 15:55             ` Ian Campbell
2015-09-26 17:30               ` Greg Kroah-Hartman
2015-09-28  9:27                 ` Ian Campbell
2015-09-28  9:43                   ` Ian Campbell
2015-10-08 22:14         ` Ben Hutchings
2015-10-09  9:15           ` Ian Campbell
2015-10-12 10:11           ` David Vrabel [this message]
2015-10-12 12:56             ` [Xen-devel] " Ben Hutchings
2015-10-12 13:01               ` David Vrabel

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=561B873E.5040803@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ben@decadent.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=ian.campbell@citrix.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=osstest-admin@xenproject.org \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).