From: Jeremy Fitzhardinge <jeremy@goop.org>
To: osth@freesurf.ch
Cc: linux-kernel@vger.kernel.org
Subject: Re: Xen kernel 2.6.23-rc7 bug at xen_mc_flush (arch/i386/xen/multicalls.c:68)
Date: Tue, 25 Sep 2007 09:48:48 -0700 [thread overview]
Message-ID: <46F93BF0.20805@goop.org> (raw)
In-Reply-To: <46D217B100015CAD@mta-fs-be-05.sunrise.ch>
osth@freesurf.ch wrote:
>> Hm, it just seems that its trying to unpin an mm on the error path of
>> execve, and so it hasn't been pinned. The simplest way to reproduce is:
>>
> ...
>
>> Anyway, try this patch.
>>
> Bug is solved by this patch. Thanks! - Maybe this patch can make it into
> 2.6.23 final?
>
Yes, I'll send it out today.
J
prev parent reply other threads:[~2007-09-25 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 21:55 Xen kernel 2.6.23-rc7 bug at xen_mc_flush (arch/i386/xen/multicalls.c:68) osth
2007-09-24 7:47 ` Jeremy Fitzhardinge
2007-09-25 0:43 ` Jeremy Fitzhardinge
2007-09-25 9:27 ` osth
2007-09-25 16:48 ` Jeremy Fitzhardinge [this message]
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=46F93BF0.20805@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osth@freesurf.ch \
/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