From: Henry Nestler <henry.nestler@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: harvey.harrison@gmail.com
Subject: Re: [PATCH 2/2] x86: Further shrink ifdef sections in fault.c
Date: Wed, 23 Apr 2008 09:20:10 +0200 [thread overview]
Message-ID: <480EE32A.1040502@henry.nestler.gmail.com> (raw)
In-Reply-To: <9PuLt-2sk-33@gated-at.bofh.it>
Ingo Molnar wrote:
> * Harvey Harrison <harvey.harrison@gmail.com> wrote:
>
>> + if (!(address >= VMALLOC_START && address < VMALLOC_END))
>> + return -1;
>
> ah, this explains the weird chunk in your other patch.
Why this is not in x86_32?
Please see my other mail "x86: endless page faults in mount_block_root
for Linux 2.6", with problem without this check.
--
Henry N.
next parent reply other threads:[~2008-04-23 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9Plf4-3KR-11@gated-at.bofh.it>
[not found] ` <9PuLt-2sk-33@gated-at.bofh.it>
2008-04-23 7:20 ` Henry Nestler [this message]
[not found] ` <480E859D.80105@arcor.de>
2008-04-23 8:05 ` [PATCH 2/2] x86: Further shrink ifdef sections in fault.c Harvey Harrison
2008-01-25 1:05 Harvey Harrison
2008-01-25 11:13 ` Ingo Molnar
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=480EE32A.1040502@henry.nestler.gmail.com \
--to=henry.nestler@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.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