On Sun, 16 Sep 2007, Randy Dunlap wrote:Actually, it's probably better that you don't change your situation unnecessarily, in case the bug goes away. Since you are triggering the problem even *without* the patch, whatever crashme is doing now for you is the interesting case. I suspect NX just isn't active for you, so the mprotect doesn't matter, but if it *does* matter, that's interesting in itself. Ahh, ok, so this is not a new thing, and it happened in 2.6.22 too. I'm really starting to suspect some early EM64T bug, and I also suspect that it's harmless but that we should just do the trivial patch to say "if the register state is in user mode, we don't care if the CPU says it was a kernel access". Linus -
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Laurent Riffard | Re: 2.6.25-rc2-mm1: WARNING at arch/x86/mm/ioremap.c:129 |
| Alan Cox | Re: x86: 4kstacks default |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 34/37] dccp: Auto-load (when supported) CCID plugins for negotiation |
| Maciej W. Rozycki | Re: [PATCH] PHYLIB: IRQ event workqueue handling fixes |
| John P Poet | Realtek 8111C transmit timed out |
git: | |
