From: Stefan Bader <stefan.bader@canonical.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [xen-4.1-testing test] 9805: regressions - FAIL
Date: Thu, 17 Nov 2011 10:57:48 +0100 [thread overview]
Message-ID: <4EC4DA9C.60600@canonical.com> (raw)
In-Reply-To: <CAEA7F2B.250F3%keir.xen@gmail.com>
On 17.11.2011 10:06, Keir Fraser wrote:
> On 17/11/2011 08:32, "Jan Beulich" <JBeulich@suse.com> wrote:
>
>> This is due to a bad backport of c/s 24007:0526644ad2a6: In -unstable,
>> evtchn_unmask() must be called with d->event_lock held, while in 4.1
>> the function acquires the lock (and now gets called with the lock already
>> held from do_physdev_op()'s case PHYSDEVOP_eoi). The change dates
>> back to 23573:584c2e5e03d9, which hardly is a candidate for backporting
>> (but maybe the locking change needs to be pulled out of there).
>
> Interestingly, Ubuntu's 4.1 fix has exactly the same problem.
>
Hm, yes we should. I am pretty sure I hit that code path often enough, Wonder
why I never saw any dead lock there...
--Stefan
> I'll revert the patch until someone has time to actually implement and test
> a working patch against our vanilla 4.1-testing tree.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-11-17 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 22:23 [xen-4.1-testing test] 9805: regressions - FAIL xen.org
2011-11-17 8:32 ` Jan Beulich
2011-11-17 9:06 ` Keir Fraser
2011-11-17 9:57 ` Stefan Bader [this message]
2011-11-17 10:13 ` Keir Fraser
2011-11-17 10:28 ` Stefan Bader
2011-11-17 10:32 ` Stefano Stabellini
2011-11-17 10:37 ` Keir Fraser
2011-11-17 10:43 ` Stefano Stabellini
2011-11-17 11:32 ` Sander Eikelenboom
2011-11-17 12:42 ` Ian Jackson
2011-11-17 20:03 ` Pasi Kärkkäinen
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=4EC4DA9C.60600@canonical.com \
--to=stefan.bader@canonical.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--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).