Re: filp_open() in 2.2.19 causes memory corruption

From: Manfred Spraul (manfred@colorfullife.com)
Date: Mon Apr 23 2001 - 15:24:55 EST

Next message: D.W.Howells: "[PATCH] rw_semaphores, optimisations try #3"
Previous message: Jeff Garzik: "Re: [PATCH] some network __init code"
Maybe in reply to: Jeff V. Merkey: "filp_open() in 2.2.19 causes memory corruption"
Next in thread: Jeff V. Merkey: "Re: filp_open() in 2.2.19 causes memory corruption"
Reply: Jeff V. Merkey: "Re: filp_open() in 2.2.19 causes memory corruption"
Reply: David Woodhouse: "Re: filp_open() in 2.2.19 causes memory corruption"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Are you sure the trace is decoded correctly?

> CPU: 0
> EIP: 0010:[sys_mremap+31/884]
> EFLAGS: 00010206

> Code: ac ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 75 d9
ac ae is
lodsb
scasb

Could you run
#objdump --disassemble-all --reloc linux/mm/mremap.o | less

and check that the code is really at offset 31 of sys_mremap?

And is it correct that only 64 MB memory is installed/enabled?

-- Manfred

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: D.W.Howells: "[PATCH] rw_semaphores, optimisations try #3"
Previous message: Jeff Garzik: "Re: [PATCH] some network __init code"
Maybe in reply to: Jeff V. Merkey: "filp_open() in 2.2.19 causes memory corruption"
Next in thread: Jeff V. Merkey: "Re: filp_open() in 2.2.19 causes memory corruption"
Reply: Jeff V. Merkey: "Re: filp_open() in 2.2.19 causes memory corruption"
Reply: David Woodhouse: "Re: filp_open() in 2.2.19 causes memory corruption"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Apr 23 2001 - 21:00:47 EST