From: Christoph Lameter <clameter@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [x86] Stricter check in follow_huge_addr()
Date: Thu, 27 Mar 2008 11:43:38 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0803271142130.7531@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080327081318.GA15626@elte.hu>
On Thu, 27 Mar 2008, Ingo Molnar wrote:
> btw., what type of real-life problem does this address? Did this trigger
> somewhere? (if yes, do you have any URLs i could put into the
> changelog?)
Does not address any issues. I just saw it on review while thinking about
how to optimize checks.
prev parent reply other threads:[~2008-03-27 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 4:03 Christoph Lameter
2008-03-27 8:13 ` Ingo Molnar
2008-03-27 18:43 ` Christoph Lameter [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=Pine.LNX.4.64.0803271142130.7531@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®