On Tue, 7 Feb 2006, Bharata B Rao wrote: > I can still crash my x86_64 box with Christoph's program. So it looks like the problem is arch specific. Test program runs fine on ia64. > page = 0xffffffffffffffd8 > &page->lru = 0000000000000000 Yup lru field overwritten as I thought. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- From: Andi Kleen <[email protected]>
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- From: Christoph Lameter <[email protected]>
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- From: Andi Kleen <[email protected]>
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- From: Bharata B Rao <[email protected]>
- Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- Prev by Date: Re: [klibc] Re: Exporting which partitions to md-configure
- Next by Date: Odd line in 2.6.16-rc2 boot sequence log
- Previous by thread: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- Next by thread: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- Index(es):
 |