Re: Memory modified after freeing in 2.5.63?

• Next message: Greg KH: "Re: [PATCH] USB speedtouch: don't race the tasklets"
• Previous message: Stephen Hemminger: "Possible FIFO race in lock_sock()"
• In reply to: Petr Vandrovec: "Memory modified after freeing in 2.5.63?"
• Next in thread: Hugh Dickins: "Re: Memory modified after freeing in 2.5.63?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Petr Vandrovec <vandrove@vc.cvut.cz> wrote:
>
> Hi,
> for some time I'm using patch attached at the end of this email,
> which modifies check_poison function to not only verify that
> last byte is POISON_END, but also that all preceeding bytes are
> either POISON_BEFORE or POISON_AFTER bytes.

Nice patch.

> And now when I returned from my month vacation and upgraded
> from 2.5.52 to 2.5.63, when dselect/apt updates dozens of packages,
> I'm getting memory corruption reports as shown below - 22nd byte
> in vm_area_struct - which looks like that VM_ACCOUNT in vm_flags
> is set after vma is freeed... Any clue? Setting VM_ACCOUNT
> in mremap.c:move_vma after calling do_unmap() looks suspicious
> to me, but as I know almost nothing about MM...

Ha! I've been harrassing Hugh over this ;)

Thanks.

-
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: Greg KH: "Re: [PATCH] USB speedtouch: don't race the tasklets"
• Previous message: Stephen Hemminger: "Possible FIFO race in lock_sock()"
• In reply to: Petr Vandrovec: "Memory modified after freeing in 2.5.63?"
• Next in thread: Hugh Dickins: "Re: Memory modified after freeing in 2.5.63?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Feb 28 2003 - 22:00:50 EST