From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Pascal Bouchareine <pascal@gandi.net>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: cannot access memory beyond end of bootstrap direct-map area
Date: Thu, 27 Aug 2009 19:55:17 +0100 [thread overview]
Message-ID: <C6BC9525.132DF%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20090827172817.GA25165@bar>
On 27/08/2009 18:28, "Pascal Bouchareine" <pascal@gandi.net> wrote:
> Investigating the above message during xen 3.3 boot, found we left
> a wrong assumption [modules_length == (mod[n].end - mod[0].start)]
> in move_memory call, leading to an access above BOOTSTRAP_DIRECTMAP_END
> and this panic on x86_32.
>
> In my understanding Keir's patch 18630 was fixing this kind of problem
> and I'm wondering why this move_memory call didn't go away with it ?
Looks like a backporting mistake. The original bug didn't happen on my
system so the bad backport wasn't noticed.
> If this were ok, attached patch fixes the panic on my system.
You should be able to remove the bogus move_memory() call, and change
absolutely nothing else. Does that also work for you? That's the change I
would check in.
-- Keir
next prev parent reply other threads:[~2009-08-27 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 17:28 cannot access memory beyond end of bootstrap direct-map area Pascal Bouchareine
2009-08-27 18:55 ` Keir Fraser [this message]
2009-08-27 21:41 ` Pascal Bouchareine
2009-08-28 6:38 ` Keir Fraser
2009-08-28 7:44 ` Pascal Bouchareine
-- strict thread matches above, loose matches on Subject: below --
2010-03-18 9:18 Cannot " Florian Wagner
2010-03-18 9:22 ` Keir Fraser
2010-03-18 22:03 ` Keir Fraser
2010-03-24 7:16 ` Florian Wagner
2010-03-24 8:35 ` Keir Fraser
2010-03-24 9:32 ` Florian Wagner
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=C6BC9525.132DF%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=pascal@gandi.net \
--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).