| 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, 08 Aug 2006 08:49:45 -0700 From: Dave Hansen <haveblue@...ibm.com> To: Kirill Korotaev <dev@...ru> Cc: Andrew Morton <akpm@...l.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Martin Schwidefsky <schwidefsky@...ibm.com>, Heiko Carstens <heiko.carstens@...ibm.com> Subject: Re: [PATCH] sys_getppid oopses on debug kernel On Tue, 2006-08-08 at 19:43 +0400, Kirill Korotaev wrote: > > Accessing freed memory is a bug, always, not just *only* when slab > > debugging is on, right? Doesn't this mean we could get junk, or that > > the reader could potentially run off a bad pointer? > no, read the comment in sys_getppid. > It is a valid optimization. _safe_ and alowing to bypass taking the lock. > BUT! This optimization relies on the fact that kernel memory (DMA + normal zone) > is always mapped into virtual address space. > Which is invalid for debug kernels only. Actually, it might also be invalid in hypervisor environments. s390 and Xen use ballooning drivers to tell the hypervisor which pages are not currently in use by the OS so that they may be used in virtual machines elsewhere. I'm cc'ing the s390 guys. Will the s390 kernel oops if it accesses a page which was ballooned back to the hypervisor? -- Dave - 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