netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [PATCH 2/2] use rtnl_lock_interruptible in 8139 to avoid shutdown ha

from [David S. Miller] [Permanent Link][Original]
To: Christoph Hellwig <hch@xxxxxx>
Subject: Re: [PATCH 2/2] use rtnl_lock_interruptible in 8139 to avoid shutdown hang
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Mon, 10 Jan 2005 13:37:14 -0800
Cc: jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20050109121630.GB19599@xxxxxx>
References: <20050109121630.GB19599@xxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx 
On Sun, 9 Jan 2005 13:16:30 +0100
Christoph Hellwig <hch@xxxxxx> wrote:

> The 8139too thread needs to use rtnl_lock_interruptible so it can avoid
> doing the actual work once it's been kill_proc()ed on module removal
> time.
> 
> Based on debugging and an earlier patch that adds a driver-private
> semaphore from Herbert Xu.

I've applied these two patches, they look perfectly fine.
Thanks Christoph.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [PATCH PKT_SCHED 0/22]: tc action cleanups, Patrick McHardy
Next by Date:  Re: [PATCH 2/2] use rtnl_lock_interruptible in 8139 to avoid shutdown hang, Christoph Hellwig
Previous by Thread:  [PATCH 2/2] use rtnl_lock_interruptible in 8139 to avoid shutdown hang, Christoph Hellwig
Next by Thread:  Re: [PATCH 2/2] use rtnl_lock_interruptible in 8139 to avoid shutdown hang, Christoph Hellwig
Indexes:  [Date] [Thread] [Top] [All Lists]