I wonder if this problem might benifit from the "breakpoint on write" capability
in kgdb. If you are using the kgdb in the mm patch, look in
Documentation/i386/kgdb/gdbinit.hw at the hwwbrk macro. You will, of course,
have to source this file from gdb to load the macro. Then you can use the gdb
command: help hwwbrk to get info on how to use it.
If the location is not written to too often this should help find the offender.
George
--
Christoph Lameter wrote:
On Tue, 10 May 2005, Oleg Nesterov wrote:
There is no corruption around ptype_all as you can see from the log. There
is a list of hex numbers which are from ptype_all -8 to ptype_all +8.
Looks okay to me.
Still ptype_all could be accessed (and corrupted) as ptype_base[16].
Christoph, could you please reboot with this patch?
Ok. I added padding before and after ptype_all.
With padding the problem no longer occurs.
However, if the padding is put before ptype_base and after ptype_all
then the problem occurs.
So it looks like this is due to writes intended for ptype_base going
out of bounds. However, there nothing in the code in net/core/dev.c
that would allow this to happen. Also why is the list head set
to 0x10:0x10?
-
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/
--
George Anzinger [email protected]
High-res-timers: http://sourceforge.net/projects/high-res-timers/
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
