linux-kernel - Re: [PATCH v2 0/4] x86: sigcontext fixes, again

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 27 Oct 2015 18:04:53 -0600
From:	Toshi Kani <toshi.kani@....com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Stas Sergeev <stsp@...t.ru>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Toshi Kani <toshi.kani@...com>, Ingo Molnar <mingo@...nel.org>
Cc:	Andy Lutomirski <luto@...capital.net>,
	Andy Lutomirski <luto@...nel.org>, X86 ML <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Brian Gerst <brgerst@...il.com>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Borislav Petkov <bp@...en8.de>,
	Stas Sergeev <stsp@...rs.sourceforge.net>
Subject: Re: [PATCH v2 0/4] x86: sigcontext fixes, again

On Wed, 2015-10-28 at 07:37 +0900, Linus Torvalds wrote:
> On Tue, Oct 27, 2015 at 11:05 PM, Stas Sergeev <stsp@...t.ru> wrote:
> > 
> > I can't easily post an Oops: under X it doesn't even appear -
> > machine freezes immediately, and under non-KMS console it is
> > possible to get one, but difficult to screen-shot (using bare
> > metal, not VM). Also the Oops was seemingly unrelated.
> > And if you run "dosemu -s" under non-KMS console, you'll also
> > reproduce this one:
> > https://bugzilla.kernel.org/show_bug.cgi?id=97321
> 
> Hmm. Andrew Morton responded to that initially, but then nothing
> happened, and now it's been another six months. Andrew?
> 
> The arch/x86/mm/pat.c error handling does seem to be suspect. This is
> all code several years old, so none of this is new, and I think Suresh
> is gone.  Adding a few other people with recent sign-offs to that
> file, in the hope that somebody feels like they own it..

In the case of PFNMAP, the range should always be mapped.  So, I wonder why
follow_phys() failed with the !pte_present() check.

Stas, do you have a test program that can reproduce 97321?

-Toshi
--
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/