On 31/10/2007, Linus Torvalds <[email protected]> wrote: > But I just rebooted and tested - the cleaned-up patch does seem to work > fine, and I get "Cannot access memory at address <xyz>" rather than any > reported problem. I can confirm the same thing here, FWIW. Cheers, Duane. -- "I never could learn to drink that blood and call it wine" - Bob Dylan - 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/
- References:
- 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- From: "Duane Griffin" <[email protected]>
- Re: 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- From: Nick Piggin <[email protected]>
- Re: 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- From: Linus Torvalds <[email protected]>
- Re: 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- From: Nick Piggin <[email protected]>
- Re: 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- From: Linus Torvalds <[email protected]>
- 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- Prev by Date: Re: [patch 0/6][RFC] Cleanup FIBMAP
- Next by Date: Re: [PATCH 1/6] Driver core: remove class_device_*_bin_file
- Previous by thread: Re: 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- Next by thread: Re: 2.6.23 regression: accessing invalid mmap'ed memory from gdb causes unkillable spinning
- Index(es):
 |