On Mon, 2006-11-13 at 20:34 +0100, Martin Lorenz wrote:
> c016ff96 <unlock_new_inode>:
> c016ff96: 83 a0 2c 01 00 00 b7 andl $0xffffffb7,0x12c(%eax)
> c016ff9d: e9 e0 ff ff ff jmp c016ff82 <wake_up_inode>
Ok, that's what I figured it had to be with that mask (though I can't
convince either of my compilers to produce that offset), so now we just
have to figure out how the heck it can get there and find a corrupted
pointer.
Can you enable frame-pointers, and capture another explosion? A more
complete trace might help. It would definitely help to reproduce
without the proprietary modules having ever been loaded.
-Mike
-
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]
