Re: [PATCH] Allow raw_notifier callouts to unregister themselves

On Thu, 11 May 2006, Andrew Morton wrote:

> 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?

No.  The patch was submitted in preparation for some work that Jes
Sorensen is doing on task notifiers.  It definitely is not needed
immediately.

Alan Stern


-
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/

---

• References:
  • Re: [PATCH] Allow raw_notifier callouts to unregister themselves
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: fix compiler warning in ip_nat_standalone.c
• Next by Date: Re: Oops in au8830 driver on x86-64
• Previous by thread: Re: [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]