From: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
To: albertito@blitiri.com.ar
Cc: llucax@gmail.com, linux-kernel@vger.kernel.org,
konishi.ryusuke@lab.ntt.co.jp, users@nilfs.org
Subject: Re: NILFS2 get stuck after bio_alloc() fail
Date: Sun, 14 Jun 2009 15:30:46 +0900 (JST) [thread overview]
Message-ID: <20090614.153046.25768784.konishi.ryusuke@gmail.com> (raw)
In-Reply-To: <20090614015240.GW30412@blitiri.com.ar>
Hi!
On Sat, 13 Jun 2009 22:52:40 -0300, Alberto Bertogli wrote:
> 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
The original GFP flag was GFP_NOIO, but replaced to GFP_NOWAIT at a
preliminary release in February 2008. It was because a user
experienced system memory shortage by the bio_alloc() call.
Even though nilfs_alloc_seg_bio() repeatedly calls bio_alloc()
reducing the number of bio vectors in case of failure, this fallback
did not work well.
I'm in two minds whether I should change it back to GFP_NOIO.
Or should I switch the gfp as follows?
Thanks,
Ryusuke Konishi
diff --git a/fs/nilfs2/segbuf.c b/fs/nilfs2/segbuf.c
index 1e68821..6b8f00a 100644
--- a/fs/nilfs2/segbuf.c
+++ b/fs/nilfs2/segbuf.c
@@ -306,6 +306,7 @@ static int nilfs_submit_seg_bio(struct nilfs_write_info *wi, int mode)
* @sb: super block
* @start: beginning disk block number of this BIO.
* @nr_vecs: request size of page vector.
+ * @gfp_mask: gfp flags
*
* alloc_seg_bio() allocates a new BIO structure and initialize it.
*
@@ -313,14 +314,14 @@ static int nilfs_submit_seg_bio(struct nilfs_write_info *wi, int mode)
* On error, NULL is returned.
*/
static struct bio *nilfs_alloc_seg_bio(struct super_block *sb, sector_t start,
- int nr_vecs)
+ gfp_t gfp_mask, int nr_vecs)
{
struct bio *bio;
- bio = bio_alloc(GFP_NOWAIT, nr_vecs);
+ bio = bio_alloc(gfp_mask, nr_vecs);
if (bio == NULL) {
while (!bio && (nr_vecs >>= 1))
- bio = bio_alloc(GFP_NOWAIT, nr_vecs);
+ bio = bio_alloc(gfp_mask, nr_vecs);
}
if (likely(bio)) {
bio->bi_bdev = sb->s_bdev;
@@ -353,9 +354,14 @@ static int nilfs_submit_bh(struct nilfs_write_info *wi, struct buffer_head *bh,
repeat:
if (!wi->bio) {
wi->bio = nilfs_alloc_seg_bio(wi->sb, wi->blocknr + wi->end,
- wi->nr_vecs);
- if (unlikely(!wi->bio))
- return -ENOMEM;
+ GFP_NOWAIT, wi->nr_vecs);
+ if (unlikely(!wi->bio)) {
+ wi->bio = nilfs_alloc_seg_bio(wi->sb,
+ wi->blocknr + wi->end,
+ GFP_NOIO, 1);
+ if (!wi->bio)
+ return -ENOMEM;
+ }
}
len = bio_add_page(wi->bio, bh->b_page, bh->b_size, bh_offset(bh));
next prev parent reply other threads:[~2009-06-14 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 1:32 Leandro Lucarella
2009-06-14 1:52 ` Alberto Bertogli
2009-06-14 6:30 ` Ryusuke Konishi [this message]
2009-06-14 7:00 ` Pekka Enberg
2009-06-14 12:34 ` 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: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
2009-06-23 4:40 ` NILFS2 get stuck after bio_alloc() fail Ryusuke Konishi
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=20090614.153046.25768784.konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@lab.ntt.co.jp \
--cc=albertito@blitiri.com.ar \
--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 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®