From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 4/6] writeback: fix writeback_inodes_wb from writeback_inodes_sb
Date: Wed, 9 Jun 2010 14:25:52 +0200 [thread overview]
Message-ID: <20100609122552.GA23216@lst.de> (raw)
In-Reply-To: <4C0E9F4B.7090204@kernel.dk>
On Tue, Jun 08, 2010 at 09:51:39PM +0200, Jens Axboe wrote:
> On 08/06/10 18.14, Christoph Hellwig wrote:
> > When we call writeback_inodes_wb from writeback_inodes_sb we always have
> > s_umount held, which currently makes the whole operation a no-op.
> >
> > But if we are called to write out inodes for a specific superblock we always
> > have s_umount held, so replace the incorrect logic checking for WB_SYNC_ALL
> > which only worked by coincidence with the proper check for an explicit
> > superblock argument.
>
> This is tons better than the pinning, I like it a lot.
Unfortunately I accidentally removed the requeue_io call when we fail
to pin the inode. This leads to softlockups after heavy I/O load.
Please fold the patch below into this one, or if not possible add it
to the end of the series.
---
From: Christoph Hellwig <hch@lst.de>
Subject: [PATCH] writeback: add missing requeue_io in writeback_inodes_wb
In "writeback: fix writeback_inodes_wb from writeback_inodes_sb" I
accidentally removed the requeue_io if we need to skip a superblock
because we can't pin it. Add it back, otherwise we're getting spurious
lockups after multiple xfstests runs.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/fs/fs-writeback.c
===================================================================
--- linux-2.6.orig/fs/fs-writeback.c 2010-06-09 12:09:42.462024800 +0200
+++ linux-2.6/fs/fs-writeback.c 2010-06-09 12:09:47.830005523 +0200
@@ -643,8 +643,10 @@ static void writeback_inodes_wb(struct b
ret = writeback_sb_inodes(sb, wb, wbc);
} else {
- if (!pin_sb_for_writeback(sb))
+ if (!pin_sb_for_writeback(sb)) {
+ requeue_io(inode);
continue;
+ }
ret = writeback_sb_inodes(sb, wb, wbc);
drop_super(sb);
}
next prev parent reply other threads:[~2010-06-09 12:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 16:14 [PATCH 0/6] writeback fixes - slow unmount and others Christoph Hellwig
2010-06-08 16:14 ` [PATCH 1/6] writeback: fix writeback completion notifications Christoph Hellwig
2010-06-08 19:50 ` Jens Axboe
2010-06-15 17:25 ` Jan Kara
2010-06-15 17:30 ` Christoph Hellwig
2010-06-08 16:14 ` [PATCH 2/6] writeback: queue work on stack in writeback_inodes_sb Christoph Hellwig
2010-06-08 19:51 ` Jens Axboe
2010-06-08 16:14 ` [PATCH 3/6] writeback: enforce s_umount locking " Christoph Hellwig
2010-06-15 17:54 ` Jan Kara
2010-06-15 17:59 ` Christoph Hellwig
2010-06-15 18:04 ` Jan Kara
2010-06-08 16:14 ` [PATCH 4/6] writeback: fix writeback_inodes_wb from writeback_inodes_sb Christoph Hellwig
2010-06-08 19:51 ` Jens Axboe
2010-06-09 12:25 ` Christoph Hellwig [this message]
2010-06-09 12:29 ` Jens Axboe
2010-06-08 16:15 ` [PATCH 5/6] writeback: simplify wakeup_flusher_threads Christoph Hellwig
2010-06-08 19:51 ` Jens Axboe
2010-06-08 16:15 ` [PATCH 6/6] writeback: simplify and split bdi_start_writeback Christoph Hellwig
2010-06-08 19:52 ` Jens Axboe
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=20100609122552.GA23216@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).