The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "David S. Miller" <davem@davemloft.net>
Cc: stern@rowland.harvard.edu, bcrl@kvack.org, akpm@osdl.org,
	sekharan@us.ibm.com, kaos@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] Notifier chain update
Date: Wed, 18 Jan 2006 23:06:25 +0000	[thread overview]
Message-ID: <1137625585.1760.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20060118.140056.39962680.davem@davemloft.net>

On Mer, 2006-01-18 at 14:00 -0800, David S. Miller wrote:
> For example, IPV6 addresses can get added/removed from a device
> in response to packets, and these operations trigger the
> inet6addr_chain notifier in net/ipv6/addrconf.c
> 
> So sleeping in a notifier is indeed illegal.

On the specific example yet. Notifiers get used for many things and
there has never been a rule about them not sleeping. There are lots of
cases where notifiers sleeping make sense including its early use in
power manglement.

Notifiers should not have locks. That was intentional in the original
implementation. You want locks, you implement them in the API *using*
the notifier, because its odds on you actually need to hold that lock
for other things too.

Alan

  parent reply	other threads:[~2006-01-18 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 16:34 [PATCH 1/8] Notifier chain update Alan Stern
2006-01-18 18:19 ` Benjamin LaHaise
2006-01-18 20:23   ` Alan Stern
2006-01-18 21:42     ` Benjamin LaHaise
2006-01-18 21:57       ` Alan Stern
2006-01-18 22:00         ` David S. Miller
2006-01-18 22:04           ` Alan Stern
2006-01-18 23:06           ` Alan Cox [this message]
2006-01-19  3:33             ` Alan Stern
2006-01-18 22:01         ` Benjamin LaHaise
2006-01-18 22:09           ` Alan Stern
2006-01-18 22:15             ` Benjamin LaHaise
2006-01-19 10:01               ` Jes Sorensen
2006-01-18 22:18             ` David S. Miller
2006-01-18 22:18               ` Benjamin LaHaise
2006-01-18 23:07       ` Alan Cox
2006-01-19  9:55       ` Jes Sorensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1137625585.1760.9.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=bcrl@kvack.org \
    --cc=davem@davemloft.net \
    --cc=kaos@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sekharan@us.ibm.com \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox