From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
brgerst@gmail.com, jolsa@redhat.com, stable@kernel.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] x86, 64-bit: Fix copy_[to/from]_user() checks for the userspace address limit
Date: Wed, 18 May 2011 22:59:52 +0200 [thread overview]
Message-ID: <20110518205952.GA25923@elte.hu> (raw)
In-Reply-To: <BANLkTimoHTmSa4LwpN-FLiEwWVLfBetV8g@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, May 18, 2011 at 1:43 PM, tip-bot for Jiri Olsa <jolsa@redhat.com> wrote:
> > As reported in BZ #30352:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=30352
> >
> > there's a kernel bug related to reading the last allowed page on x86_64.
>
> Btw, I think this message is very misleading.
>
> It has nothing what-so-ever to do with "the last allowed page".
Yeah, i noticed that and this is why i added this bit from Brian's explanation
to the end of the commit:
The bug is that the last byte before the guard page can't be read
because of the off-by-one error. The guard page is left in place.
I should have fixed the original changelog instead of trying to clarify it via
appending it ...
Thanks,
Ingo
prev parent reply other threads:[~2011-05-18 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 14:30 [PATCH] x86, x86_64: Fix checks for " Jiri Olsa
2011-05-16 11:42 ` Ingo Molnar
2011-05-18 4:48 ` Brian Gerst
2011-05-18 8:12 ` Ingo Molnar
2011-05-18 10:08 ` Linus Torvalds
2011-05-18 10:39 ` Ingo Molnar
2011-05-18 20:43 ` [tip:perf/core] x86, 64-bit: Fix copy_[to/from]_user() checks for the " tip-bot for Jiri Olsa
2011-05-18 20:54 ` Linus Torvalds
2011-05-18 20:59 ` Ingo Molnar [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=20110518205952.GA25923@elte.hu \
--to=mingo@elte.hu \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®