Re: [PATCH] Allow raw_notifier callouts to unregister themselves

Alan Stern <[email protected]> wrote:
>
> Since raw_notifier chains don't benefit from any centralized locking
> protections, they shouldn't suffer from the associated limitations.  
> Under some circumstances it might make sense for a raw_notifier callout
> routine to unregister itself from the notifier chain.  This patch (as678)
> changes the notifier core to allow for such things.

ok...  Can you see any reason why 2.6.17 needs this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] Allow raw_notifier callouts to unregister themselves
  - From: "David S. Miller" <[email protected]>
- Re: [PATCH] Allow raw_notifier callouts to unregister themselves
  - From: Alan Stern <[email protected]>

References:
- [PATCH] Allow raw_notifier callouts to unregister themselves
  - From: Alan Stern <[email protected]>

Prev by Date: Re: + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree
Next by Date: Re: [openib-general] [PATCH 6/6] iSER Kconfig and Makefile
Previous by thread: [PATCH] Allow raw_notifier callouts to unregister themselves
Next by thread: Re: [PATCH] Allow raw_notifier callouts to unregister themselves
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]