Date: Mon, 09 Jun 2003 16:39:15 -0700 (PDT)
Message-Id: <20030609.163915.74729355.davem@redhat.com>
To: zippel@linux-m68k.org
Cc: wa@almesberger.net, chas@cmf.nrl.navy.mil, 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: <Pine.LNX.4.44.0306100129460.12110-100000@serv>
References: <Pine.LNX.4.44.0306100113420.12110-100000@serv>
	<20030609.161435.104053652.davem@redhat.com>
	<Pine.LNX.4.44.0306100129460.12110-100000@serv>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 593
Lines: 13

   From: Roman Zippel <zippel@linux-m68k.org>
   Date: Tue, 10 Jun 2003 01:34:19 +0200 (CEST)

   You also have to wait for the already running 
   operations to finish, before you can allow the module to unload.

These things run under dev_base_lock, so either they find the device
or they don't, and since they hold a spinlock they can't preempt.
-
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/