Date: Mon, 09 Jun 2003 07:00:14 -0700 (PDT)
Message-Id: <20030609.070014.118613484.davem@redhat.com>
To: chas@cmf.nrl.navy.mil
Cc: baldrick@wanadoo.fr, wa@almesberger.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations
 (take 2) 
From: "David S. Miller" <davem@redhat.com>
In-Reply-To: <200306091400.h59E0bsG022093@ginger.cmf.nrl.navy.mil>
References: <20030609.063825.123987226.davem@redhat.com>
	<200306091400.h59E0bsG022093@ginger.cmf.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 932
Lines: 25

   From: chas williams <chas@cmf.nrl.navy.mil>
   Date: Mon, 09 Jun 2003 09:58:45 -0400

   >ATM should unlink them immediately, and mark them dead.
   >Anything that tries to do something with a VCC should
   >check that it is still alive.
   
   i imagine marking vcc->dev = NULL would be pretty close to the above.

Yep.  That'd work.

   (see latest rfc patch).
   
You do know that won't compile with current 2.5.x right?
All the struct sock members got renamed to have a "sk_" prefix
2 days ago :-)

But I did like the general direction you were going in.  I can't
comment on things like getting rid of ATM_*_ITF or whatever it's
called because I don't know what that thing does ;)
-
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/