| 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
| ||
|
Message-ID: <817ecb6f1003021003s4000fa4j1b357de0833db9ed@mail.gmail.com> Date: Tue, 2 Mar 2010 13:03:14 -0500 From: Siarhei Liakh <sliakh.lkml@...il.com> To: castet.matthieu@...e.fr Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [tip:x86/mm] x86, mm: NX protection for kernel data On Tue, Mar 2, 2010 at 12:51 PM, Siarhei Liakh <sliakh.lkml@...il.com> wrote: >>> At this point I need some help and guidance on how to track down what >>> exactly happens there, as I am not very familiar with what goes into >>> .data and why are we trying to execute it. >> Can't you add debug printk in the fault handler before any exception processing >> >> Something like that. > > That does not really give any additional information. The message does > not show up in the output and the stack trace says that we are somehow > ended up in doublefault_fn. Forgot to add one more thing: it looks like fault on instruction prefetch is already taken care of in fault handlers and should generate an appropriate message. The way I interpret the fact that doublefault_fn is the one that prints out a message, is that main fault handler is somehow dependent on .data being executable.... (but this is pure speculation on my part at this point)... -- 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