mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Magnus Damm" <magnus.damm@gmail.com>
To: vgoyal@in.ibm.com
Cc: "Magnus Damm" <magnus@valinux.co.jp>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
	ebiederm@xmission.com
Subject: Re: [Fastboot] [PATCH] kexec: Avoid overwriting the current pgd (i386)
Date: Tue, 2 May 2006 10:35:18 +0900	[thread overview]
Message-ID: <aec7e5c30605011835g3a0a671br2b327909e2d6443c@mail.gmail.com> (raw)
In-Reply-To: <20060501143512.GA7129@in.ibm.com>

On 5/1/06, Vivek Goyal <vgoyal@in.ibm.com> wrote:
> On Mon, May 01, 2006 at 06:49:16PM +0900, Magnus Damm wrote:
> > kexec: Avoid overwriting the current pgd (i386)
> >
> > This patch upgrades the i386-specific kexec code to avoid overwriting the
> > current pgd. Overwriting the current pgd is bad when CONFIG_CRASH_DUMP is used
> > to start a secondary kernel that dumps the memory of the previous kernel.
> >
> > The code introduces a new set of page tables called "page_table_a". These
> > tables are used to provide an executable identity mapping without overwriting
> > the current pgd.
>
> True, current pgd is overwritten but that effects only user space mappings
> and currently "crash" supports only backtracing kernel space code. But at
> the same time probably it is not a bad idea to maintain a separate page
> table and switch to that instead of overwriting the existing pgd. This
> shall help if in future user space backtracing is also supported.

I agree, but I also think that overwriting user space mappings is bad
from the trace perspective too, especially if you look at kernel data.
I would say that user space page tables are just another kernel data
structure, and overwriting them may result in things like inconsistent
page->mapcount values.

Thanks for the comments,

/ magnus

      parent reply	other threads:[~2006-05-02  1:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01  9:49 Magnus Damm
2006-05-01 14:35 ` [Fastboot] " Vivek Goyal
2006-05-01 16:37   ` Eric W. Biederman
2006-05-02  1:56     ` Magnus Damm
2006-05-02  7:15       ` Eric W. Biederman
2006-05-02  8:01         ` Magnus Damm
2006-05-02  1:35   ` Magnus Damm [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=aec7e5c30605011835g3a0a671br2b327909e2d6443c@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=magnus@valinux.co.jp \
    --cc=vgoyal@in.ibm.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

all inboxes | Powered by JetHome®