From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
"Thomas Meyer" <thomas@m3y3r.de>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: -git: BUG: unable to handle kernel paging request at c0100248 [CPU hotplug]
Date: Sun, 27 Jul 2008 21:35:27 +0200 [thread overview]
Message-ID: <19f34abd0807271235q516fc2e1rc43c6736044eabfc@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807272118460.574@apollo.tec.linutronix.de>
On Sun, Jul 27, 2008 at 9:23 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Sun, 27 Jul 2008, Vegard Nossum wrote:
>> Booting processor 1/1 ip 6000
>> Initializing CPU#1
>> [...]
>> Write protecting the kernel text: 5648k
>>
>> So it succeeds because the protection happens much later :-)
>
> Patch below fixes the issue. I get it to Linus ASAP.
Nice :)
[...]
> +.section .cpuinit.data,"wa"
> +.align 4
> +ENTRY(initial_code)
> + .long i386_start_kernel
> +
> .section .text
> /*
> * Real beginning of normal "text" segment
>
Hm, isn't there some kind of "section stack" that can be used to
restore the previous section? .pushsection/.popsection directives?
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-27 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 9:55 Vegard Nossum
2008-07-27 10:07 ` Vegard Nossum
2008-07-27 17:14 ` Dmitry Adamushko
2008-07-27 17:19 ` Vegard Nossum
2008-07-27 19:23 ` Thomas Gleixner
2008-07-27 19:35 ` Vegard Nossum [this message]
2008-07-27 19:40 ` Vegard Nossum
2008-07-28 18:34 ` Glauber Costa
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=19f34abd0807271235q516fc2e1rc43c6736044eabfc@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=x86@kernel.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 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®