All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alberto Bertogli <albertito@blitiri.com.ar>
To: Leandro Lucarella <llucax@gmail.com>
Cc: linux-kernel@vger.kernel.org, konishi.ryusuke@lab.ntt.co.jp,
	users@nilfs.org
Subject: Re: NILFS2 get stuck after bio_alloc() fail
Date: Sat, 13 Jun 2009 22:52:40 -0300	[thread overview]
Message-ID: <20090614015240.GW30412@blitiri.com.ar> (raw)
In-Reply-To: <20090614013211.GA22552@homero.springfield.home>

On Sat, Jun 13, 2009 at 10:32:11PM -0300, Leandro Lucarella wrote:
> Hi!
> 
> While testing nilfs2 (using 2.6.30) doing some "cp"s and "rm"s, I noticed
> sometimes they got stucked in D state, and the kernel had said the
> following message:
> 
>         NILFS: IO error writing segment
> 
> A friend gave me a hand and after adding some printk()s we found out that
> the problem seems to occur when bio_alloc()s inside nilfs_alloc_seg_bio()
> fail, making it return NULL; but we don't know how that causes the
> processes to get stucked.

By the way, those bio_alloc()s are using GFP_NOWAIT but it looks like they
could use at least GFP_NOIO or GFP_NOFS, since the caller can (and sometimes
do) sleep. The only caller is nilfs_submit_bh(), which calls
nilfs_submit_seg_bio() which can sleep calling wait_for_completion(). Is there
something I'm missing?

Thanks a lot,
		Alberto

  reply	other threads:[~2009-06-14  1:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14  1:32 NILFS2 get stuck after bio_alloc() fail Leandro Lucarella
2009-06-14  1:52 ` Alberto Bertogli [this message]
2009-06-14  6:30   ` Ryusuke Konishi
2009-06-14  7:00     ` Pekka Enberg
2009-06-14 12:34       ` Ryusuke Konishi
2009-06-14  3:45 ` Ryusuke Konishi
2009-06-14  3:45   ` Ryusuke Konishi
2009-06-14 15:32   ` Leandro Lucarella
2009-06-14 18:02     ` Ryusuke Konishi
2009-06-14 18:02       ` Ryusuke Konishi
2009-06-14 18:13       ` Leandro Lucarella
2009-06-18 17:34         ` [PATCH] nilfs2: fix hang problem after bio_alloc() failed Ryusuke Konishi
2009-06-21 11:08           ` Andi Kleen
2009-06-21 12:34             ` [NILFS users] " Ryusuke Konishi
     [not found]         ` <20090614181313.GA16597-ukiYB341y+1jWMeXa1+QZ5bDTtF7IOEM@public.gmane.org>
2009-06-23  4:40           ` NILFS2 get stuck after bio_alloc() fail Ryusuke Konishi
2009-06-23  4:40             ` Ryusuke Konishi
     [not found]             ` <20090623.134026.08265083.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-06-23 12:55               ` Leandro Lucarella
2009-06-23 12:55                 ` Leandro Lucarella

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=20090614015240.GW30412@blitiri.com.ar \
    --to=albertito@blitiri.com.ar \
    --cc=konishi.ryusuke@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llucax@gmail.com \
    --cc=users@nilfs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.