From: Wanpeng Li <liwp.linux@gmail.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Gavin Shan <shangw@linux.vnet.ibm.com>,
Wanpeng Li <liwp.linux@gmail.com>
Subject: [PATCH V2] writeback: fix hung_task alarm when sync block
Date: Wed, 13 Jun 2012 12:42:33 +0800 [thread overview]
Message-ID: <1339562553-10035-1-git-send-email-liwp.linux@gmail.com> (raw)
Hi Fengguang,
This time it works well after testing.
Regards,
Wanpeng Li
From: Wanpeng Li <liwp@linux.vnet.ibm.com>
"V1 -> V2"
* remove redundant hangcheck variable
I use several dd processes to write a slow SD card
dd if=/dev/sda1 of=/dev/sdc4 bs=1M count=4000
and several sync commands(maybe > 10),dmesg show this:
[ 366.888741] INFO: task sync:3518 blocked for more than 120 seconds.
[ 366.888742] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 366.888746] sync D 00000201 0 3518 3462 0x00000000
[ 366.888752] dcde5e54 00000082 00000000 00000201 00000000 c180d220 c1933d00 c1933d00
[ 366.888758] 614a7ae7 00000023 f6bc0d00 ebecb280 c180d220 f6bc0d6c f04acbfc 00000000
[ 366.888786] f6bc0d6c dcde5e2c 00000023 f6bc0d44 00000000 00000000 ebd8b2b4 dcde5e6c
[ 366.888788] Call Trace:
[ 366.888792] [<c107a0ee>] ? enqueue_entity+0xee/0x5a0
[ 366.888795] [<c15abc83>] schedule+0x23/0x60
[ 366.888798] [<c15aa5ad>] schedule_timeout+0x22d/0x2a0
[ 366.888801] [<c1071ce2>] ? check_preempt_curr+0x72/0x90
[ 366.888804] [<c1071d28>] ? ttwu_do_wakeup+0x28/0x130
[ 366.888807] [<c1037f28>] ? default_spin_lock_flags+0x8/0x10
[ 366.888810] [<c15acaad>] ? _raw_spin_lock_irqsave+0x2d/0x40
[ 366.888813] [<c15abb17>] wait_for_common+0xa7/0x110
[ 366.888816] [<c1074690>] ? try_to_wake_up+0x220/0x220
[ 366.888819] [<c15abc57>] wait_for_completion+0x17/0x20
[ 366.888822] [<c116ad80>] writeback_inodes_sb_nr+0x70/0x90
[ 366.888825] [<c116af75>] writeback_inodes_sb+0x25/0x30
[ 366.888828] [<c117159f>] __sync_filesystem+0x4f/0x90
[ 366.888831] [<c11715f7>] sync_one_sb+0x17/0x20
[ 366.888834] [<c114c430>] iterate_supers+0xc0/0xd0
[ 366.888837] [<c11715e0>] ? __sync_filesystem+0x90/0x90
[ 366.888831] [<c11715f7>] sync_one_sb+0x17/0x20
[ 366.888834] [<c114c430>] iterate_supers+0xc0/0xd0
[ 366.888837] [<c11715e0>] ? __sync_filesystem+0x90/0x90
[ 366.888840] [<c117167b>] sys_sync+0x2b/0x60
[ 366.888842] [<c15b385f>] sysenter_do_call+0x12/0x28
Too many similar messages flood the logs. So I use a present method to
fix this issue.
------------------------------------------
Author: Mark Lord <kernel@teksavvy.com>
Date: Fri Sep 24 09:51:13 2010 -0400
block: Prevent hang_check firing during long I/O
------------------------------------------
Signed-off-by: Wanpeng Li <liwp.linux@gmail.com>
---
fs/fs-writeback.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
index f2d0109..df879ee 100644
--- a/fs/fs-writeback.c
+++ b/fs/fs-writeback.c
@@ -1311,7 +1311,11 @@ void writeback_inodes_sb_nr(struct super_block *sb,
WARN_ON(!rwsem_is_locked(&sb->s_umount));
bdi_queue_work(sb->s_bdi, &work);
- wait_for_completion(&done);
+ if (sysctl_hung_task_timeout_secs)
+ while (!wait_for_completion_timeout(&done, HZ/2))
+ ;
+ else
+ wait_for_completion(&done);
}
EXPORT_SYMBOL(writeback_inodes_sb_nr);
--
1.7.9.5
next reply other threads:[~2012-06-13 4:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 4:42 Wanpeng Li [this message]
2012-06-13 14:27 ` [PATCH V2] writeback: fix hung_task alarm when sync block Jeff Moyer
2012-06-13 14:48 ` Fengguang Wu
2012-06-13 14:55 ` Fengguang Wu
2012-06-13 15:34 ` Jeff Moyer
2012-06-14 13:36 ` Fengguang Wu
2012-06-19 20:14 ` Jeff Moyer
2012-06-19 21:02 ` Dave Chinner
2012-06-19 21:09 ` Jeff Moyer
2012-06-19 21:56 ` Dave Chinner
2012-06-14 1:35 ` Wanpeng Li
2012-06-14 13:26 ` Fengguang Wu
2012-06-15 22:43 ` Dave Chinner
2012-06-14 10:52 ` Wanpeng Li
2012-06-15 22:38 ` Dave Chinner
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=1339562553-10035-1-git-send-email-liwp.linux@gmail.com \
--to=liwp.linux@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shangw@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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.