Re: [PATCH][2.6] e100_phy.c uses free'd .text after init

netdev

Re: [PATCH][2.6] e100_phy.c uses free'd .text after init

To:	Zwane Mwaikambo <zwane@xxxxxxxxxxxxxxxx>
Subject:	Re: [PATCH][2.6] e100_phy.c uses free'd .text after init
From:	Anton Blanchard <anton@xxxxxxxxx>
Date:	Sun, 30 Nov 2003 09:35:52 +1100
Cc:	Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to:	<Pine.LNX.4.58.0311290033120.1674@xxxxxxxxxxxxxxxxxxxxx>
References:	<Pine.LNX.4.58.0311290033120.1674@xxxxxxxxxxxxxxxxxxxxx>
Sender:	netdev-bounce@xxxxxxxxxxx
User-agent:	Mutt/1.5.4i

Hi Zwane,

> This was causing an oops when using mii-tool due to the .text being free'd
> after initialisation.

We stumbled across this a few weeks ago, Jeff's BK tree should have a
fix.

Anton

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH][2.6] e100_phy.c uses free'd .text after init, Zwane Mwaikambo Re: [PATCH][2.6] e100_phy.c uses free'd .text after init, Anton Blanchard <= Re: [PATCH][2.6] e100_phy.c uses free'd .text after init, Jeff Garzik

Previous by Date:	Re: [SCTP] Fix incestuous header relations, Herbert Xu
Next by Date:	Re: [PATCH] 2.6.0-test11-bk27-netdrvr-exp1 - r8169 update, Francois Romieu
Previous by Thread:	[PATCH][2.6] e100_phy.c uses free'd .text after init, Zwane Mwaikambo
Next by Thread:	Re: [PATCH][2.6] e100_phy.c uses free'd .text after init, Jeff Garzik
Indexes:	[Date] [Thread] [Top] [All Lists]