From: Doug Ledford <dledford@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Patrick Mansfield <patmans@us.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: GFP_ATOMIC allocations...
Date: Thu, 29 Aug 2002 11:58:12 -0400 [thread overview]
Message-ID: <20020829115812.A31625@redhat.com> (raw)
In-Reply-To: <1030618075.7290.110.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 29, 2002 at 11:47:55AM +0100
On Thu, Aug 29, 2002 at 11:47:55AM +0100, Alan Cox wrote:
> On Thu, 2002-08-29 at 02:42, Doug Ledford wrote:
> > > Do GFP_KERNEL alloc failures during boot time just return NULL?
> >
> > GFP_ATOMIC returns NULL on failure, GFP_KERNEL *should* never fail until
> > we get to a true OOM condition because it will block and wait for the vm
> > subsystem to free us up some space. Under true OOM conditions it will
> > return NULL AFAIK.
>
> Or maybe deadlock if its happening due to I/O.
That would be a trick indeed since Patrick and I were referring to the
scanning code so the device isn't even configured for kernel use yet :-P
> If it wants to flush a
> page out to that scsi device and the scsi device is doing the allocation
> life gets very unpleasant.
Of course. This is why the mid layer doesn't typically allocate anything
at all once initial setup of a device is complete. No allocations once
setup is complete means no deadlock.
> SCSI may not be coming from block layer
> access with PF_MEM* set either, think about /proc and scsi-generic
>
> "Here be dragons"
That's why I recommended people think each use through instead of blindly
changing things ;-)
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-08-29 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 0:25 GFP_ATOMIC allocations Doug Ledford
2002-08-29 0:47 ` Patrick Mansfield
2002-08-29 1:42 ` Doug Ledford
2002-08-29 10:47 ` Alan Cox
2002-08-29 15:58 ` Doug Ledford [this message]
2002-08-29 17:10 ` Patrick Mansfield
2002-08-30 16:22 ` Patrick Mansfield
2002-08-30 16:46 ` James Bottomley
2002-08-30 18:58 ` Doug Ledford
2002-08-30 21:55 ` [PATCH] " Patrick Mansfield
2002-09-03 14:57 ` James Bottomley
2002-09-03 16:07 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 15:59 Bryan Henderson
2002-08-29 16:25 ` Doug Ledford
2002-08-29 16:50 ` Alan Cox
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=20020829115812.A31625@redhat.com \
--to=dledford@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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