From: David Vrabel <david.vrabel@citrix.com>
To: Dave Scott <Dave.Scott@citrix.com>,
David Vrabel <david.vrabel@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
John Else <john.else@citrix.com>,
Anil Madhavapeddy <anil@recoil.org>
Subject: Re: xc_gntshr_unmap problems (BUG(s) in xen-gntalloc?)
Date: Mon, 1 Sep 2014 11:19:18 +0100 [thread overview]
Message-ID: <54044826.1070107@citrix.com> (raw)
In-Reply-To: <F3FC4933-3514-489D-BCE0-2DA5D042D0E0@citrix.com>
On 29/08/14 22:15, Dave Scott wrote:
> Hi,
>
> On 29 Aug 2014, at 15:05, David Vrabel <david.vrabel@citrix.com> wrote:
>
>> On 29/08/14 13:40, Dave Scott wrote:
>>> Hi,
>>>
>>> On 28 Aug 2014, at 14:50, David Vrabel <david.vrabel@citrix.com> wrote:
>>>
>>>> Does this patch fix the oops?
>>>
>>> Yes, I’ve left my test case running for several hours with no sign of trouble.
>>
>> Thanks. I'll take that as a
>>
>> Tested-by: Dave Scott <david.scott@citrix.com>
>
> I just realised that my tests weren’t as clear-cut as I hoped. When
> I rebuilt my ubuntu kernel I accidentally got a free upgrade from 3.2 to
> 3.13, so what I actually tested was:
>
> 3.2: kernel oops triggered easily
> 3.13 plus your patch: seems solid
>
> I could go back and test 3.13 minus your patch if that would be helpful.
Please. I can't seem to easily trigger the race on my test system. How
long does it take to fail typically in your case?
David
next prev parent reply other threads:[~2014-09-01 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:33 xc_gntshr_unmap problems (BUG(s) in xen-gntalloc?) Dave Scott
2014-08-28 13:50 ` David Vrabel
2014-08-29 12:40 ` Dave Scott
2014-08-29 14:05 ` David Vrabel
2014-08-29 16:46 ` Dave Scott
2014-08-29 21:15 ` Dave Scott
2014-09-01 10:19 ` David Vrabel [this message]
2014-09-02 9:13 ` Dave Scott
2014-09-02 13:55 ` 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=54044826.1070107@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Dave.Scott@citrix.com \
--cc=anil@recoil.org \
--cc=boris.ostrovsky@oracle.com \
--cc=john.else@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.