linux-kernel - Re: [tip:perf/core] x86, 64-bit: Fix copy_[to/from]_user() checks for the userspace address limit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110518205952.GA25923@elte.hu>
Date:	Wed, 18 May 2011 22:59:52 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	brgerst@...il.com, jolsa@...hat.com, stable@...nel.org,
	tglx@...utronix.de, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] x86, 64-bit: Fix copy_[to/from]_user() checks
 for the userspace address limit


* Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Wed, May 18, 2011 at 1:43 PM, tip-bot for Jiri Olsa <jolsa@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/