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
| ||
|
Date: Tue, 30 Sep 2014 08:52:08 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Dave Jones <davej@...hat.com>, Al Viro <viro@...iv.linux.org.uk>, Linux Kernel <linux-kernel@...r.kernel.org>, Rik van Riel <riel@...hat.com> Cc: Ingo Molnar <mingo@...hat.com>, Michel Lespinasse <walken@...gle.com> Subject: Re: pipe/page fault oddness. On Mon, Sep 29, 2014 at 9:54 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > Odd. The 0x3b3 offset seems to be the single-byte write of zero, which is > just the initial probe (aka "fault_in_pages_writeable()"). > > How *that* could loop, I have no idea. Unless the exception table is broken. > I'll take another look tomorrow. Confirmed. It's the second write in fault_in_pages_writeable() (the one that writes to the "end" pointer). And there's no loop in software. And in fact, the trace shows that there is no exception case for the fault either, so the fault is perfectly successful. So if it's looping on that fault, what seems to happen is that the page fault keeps happening. Can you recreate this? Because if you can, please try to revert commit e4a1cc56e4d7 ("x86: mm: drop TLB flush from ptep_set_access_flags"). Maybe the TLB has it read-only, and it doesn't get flushed, and the page fault happens over and over again. What kind of CPU is the problematic machine? There was some question about just how architectural the whole "TLB entry causing a page fault gets invalidated automatically" really is. Linus -- 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/
Powered by blists - more mailing lists