[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20110721.212950.1991725607632413241.davem@davemloft.net>
Date: Thu, 21 Jul 2011 21:29:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mst@...hat.com
Cc: krkumar2@...ibm.com, rusty@...tcorp.com.au, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, shemminger@...tta.com
Subject: Re: [PATCH repost] Fix panic in virtnet_remove
From: "Michael S. Tsirkin" <mst@...hat.com>
Date: Wed, 20 Jul 2011 17:31:15 +0300
> On Wed, Jul 20, 2011 at 07:26:02PM +0530, Krishna Kumar wrote:
>> Fix a panic in virtnet_remove. unregister_netdev has already
>> freed up the netdev (and virtnet_info) due to dev->destructor
>> being set, while virtnet_info is still required. Remove
>> virtnet_free altogether, and move the freeing of the per-cpu
>> statistics from virtnet_free to virtnet_remove.
>>
>> Tested patch below.
>>
>> Signed-off-by: Krishna Kumar <krkumar2@...ibm.com>
>
> Also note that the crash was apparently introduced by
> 3fa2a1df909482cc234524906e4bd30dee3514df in net-next,
> so this is a net-next only patch.
>
> Stephen, was there any special reason to free the memory
> in the destructor like you did?
>
> Acked-by: Michael S. Tsirkin <mst@...hat.com>
Applied.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists