From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: GFP_ATOMIC/GFP_KERNEL broken for use by block devices!!
Date: Mon, 24 Oct 2005 19:03:52 -0400 [thread overview]
Message-ID: <20051024230352.GA11467@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200510221838.17065.blaisorblade@yahoo.it>
On Sat, Oct 22, 2005 at 06:38:16PM +0200, Blaisorblade wrote:
> In the write path of a ???lesystem, using
> GFP_KERNEL or GFP_ATOMIC will lead to deadlocks
> eventually. [...] GFP_NOFS is there for a reason, as is GFP_NOIO for block
> device drivers.
I know about this, and this is another reason I'm not sending it in. I
don't really understand it either. If GFP_ATOMIC can block, then I don't
know what good it is.
> Which means that we _must_ ask for help from somebody else.
Yup.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-10-24 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 16:38 [uml-devel] GFP_ATOMIC/GFP_KERNEL broken for use by block devices!! Blaisorblade
2005-10-24 23:03 ` Jeff Dike [this message]
2005-10-24 23:30 ` [uml-devel] " Blaisorblade
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=20051024230352.GA11467@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.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