public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] udf: reduce stack usage of udf_get_filename
Date: Wed, 19 Nov 2008 09:35:15 -0800	[thread overview]
Message-ID: <20081119093515.9c807f71.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081119152622.GB29820@duck.suse.cz>

On Wed, 19 Nov 2008 16:26:22 +0100 Jan Kara <jack@suse.cz> wrote:

> On Tue 18-11-08 16:19:38, Andrew Morton wrote:
> > On Sun, 16 Nov 2008 19:02:45 +0100
> > Marcin Slusarz <marcin.slusarz@gmail.com> wrote:
> > 
> > > +	filename = kmalloc(sizeof(struct ustr), GFP_NOFS);
> > 
> > I suspect that we could have used the superior GFP_KERNEL everywhere in
> > both these patches.  But I'll let Jan worry about that ;)
>   Definitely not in the second case - that one is called from inside
> readdir, lookup and symlink resolution code so that could lead to deadlocks
> IMHO.
>   Regarding the first case in process_sequence, that is called only from
> udf_fill_super(). So there it might be safe to use GFP_KERNEL but I'm not
> quite sure either... So I'd leave GFP_NOFS there.
> 

The reason for using GFP_NOFS is to prevent deadlocks when direct
memory reclaim reenters the filesystem code.  But I don't think there's
ever a case when direct reclaim would enter the namespace part of a
filesystem - it is only expected to touch the pagecache (ie: data)
operations: writepage(), block allocator, etc.



  reply	other threads:[~2008-11-19 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 18:02 [PATCH 2/2] udf: reduce stack usage of udf_get_filename Marcin Slusarz
2008-11-19  0:19 ` Andrew Morton
2008-11-19 15:26   ` Jan Kara
2008-11-19 17:35     ` Andrew Morton [this message]
2008-11-19 21:01       ` Jan Kara
2008-11-19 21:37         ` Andrew Morton
2008-11-19 15:54 ` Jan Kara

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=20081119093515.9c807f71.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.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