From: Tim Hockin <thockin@hockin.org>
To: Mike Waychison <Michael.Waychison@Sun.COM>
Cc: Ian Kent <raven@themaw.net>, Ingo Oeser <ioe-lkml@rameria.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] RE: [autofs] multiple servers per automount
Date: Thu, 23 Oct 2003 10:09:42 -0700 [thread overview]
Message-ID: <20031023170942.GA2895@hockin.org> (raw)
In-Reply-To: <3F980949.1040201@sun.com>
On Thu, Oct 23, 2003 at 01:00:57PM -0400, Mike Waychison wrote:
> >Would a GFP_ATOMIC make a difference to the analysis?
> Yes, sleeping within a spinlock is bad practice because it may
> eventually deadlock. Pretend that the lock is taken, the call to
> kmalloc is made, the mm system doesn't have any immidiately free memory
> and through some flow of execution requires that a some pseudo-block
> device backed filesystem needs to be mounted -> deadlock. I have no
> idea if this is currently a likely scenario, however not sleeping within
> a lock is 'The Right Thing' and should be avoided at all costs.
it's worse than that. It's forbidden. It's a VERY likely deadlock scenario
in the general sense, even if this particular case is not. If you need to
lock something and you need to sleep holding that lock, use a semaphore.
--
Notice that as computers are becoming easier and easier to use,
suddenly there's a big market for "Dummies" books. Cause and effect,
or merely an ironic juxtaposition of unrelated facts?
next prev parent reply other threads:[~2003-10-23 17:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0310142131090.3044-100000@raven.themaw.net>
2003-10-14 15:52 ` Mike Waychison
2003-10-14 20:44 ` H. Peter Anvin
2003-10-14 23:12 ` Mike Waychison
2003-10-15 10:28 ` Ingo Oeser
2003-10-15 16:16 ` Mike Waychison
2003-10-23 13:37 ` Ian Kent
2003-10-23 17:00 ` Mike Waychison
2003-10-23 17:09 ` Tim Hockin [this message]
2003-10-24 0:47 ` Ian Kent
2003-10-24 1:42 ` Tim Hockin
2003-10-15 7:22 ` Ian Kent
2003-10-15 14:31 Lever, Charles
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=20031023170942.GA2895@hockin.org \
--to=thockin@hockin.org \
--cc=Michael.Waychison@Sun.COM \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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
all inboxes | Powered by JetHome®