Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)

From: David S. Miller (davem@redhat.com)
Date: Mon Jun 09 2003 - 18:39:15 EST

Next message: Nick Piggin: "Re: [PATCH] io stalls"
Previous message: john stultz: "Re: [PATCH] Some clean up of the time code."
In reply to: Roman Zippel: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Next in thread: Roman Zippel: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Reply: Roman Zippel: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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/

Next message: Nick Piggin: "Re: [PATCH] io stalls"
Previous message: john stultz: "Re: [PATCH] Some clean up of the time code."
In reply to: Roman Zippel: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Next in thread: Roman Zippel: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Reply: Roman Zippel: "Re: [PATCH][ATM] use rtnl_{lock,unlock} during device operations (take 2)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:22 EST