linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: He YunLei <heyunlei@huawei.com>
To: Chao Yu <chao2.yu@samsung.com>,
	jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: 'Biao He' <hebiao6@huawei.com>
Subject: Re: [PATCH] f2fs: avoid hungtask problem caused by losing wake_up
Date: Tue, 23 Feb 2016 15:02:40 +0800	[thread overview]
Message-ID: <56CC0410.50103@huawei.com> (raw)
In-Reply-To: <009501d16dfd$52a518c0$f7ef4a40$@samsung.com>

On 2016/2/23 13:44, Chao Yu wrote:
> Hi Yunlei,
Hi Chao,
>
>> -----Original Message-----
>> From: Yunlei He [mailto:heyunlei@huawei.com]
>> Sent: Tuesday, February 23, 2016 12:08 PM
>> To: chao2.yu@samsung.com; jaegeuk@kernel.org; linux-f2fs-devel@lists.sourceforge.net
>> Cc: bintian.wang@huawei.com; Yunlei He; Biao He
>> Subject: [f2fs-dev] [PATCH] f2fs: avoid hungtask problem caused by losing wake_up
>>
>> The D state of wait_on_all_pages_writeback should be waken by
>> function f2fs_write_end_io when all writeback pages have been
>> succesfully written to device. It's possible that wake_up comes
>> between get_pages and io_schedule. Maybe in this case it will
>> lost wake_up and still in D state even if all pages have been
>> write back to device, and finally, the whole system will be into
>> the hungtask state.
>
> I haven't encountered such issue so far, do you suffer this in real
> world?
>
yes, I have encounter it, the whole file system is blocked at function
wait_on_all_pages_writeback beyond 120s when write cp, and no error reported
by storage device driver.
>>
>>                  if (!get_pages(sbi, F2FS_WRITEBACK))
>>                           break;
>> 					<---------  wake_up
>
> wake_up will put all tasks linked in sbi->cp_wait on run-queue, so
> here it should be save to call io_schedule, after being rescheduled,
> it will get the chance to check above condition to break out.
>
> Thanks,

Here, we just doubt something weird may cause wait_on_all_pages_writeback
could not be waken. Wake_up trigger only one time by last bio's end_io
function, if the thread happen to miss it, the thread will be in D state
forever. So we change the code to make wait_on_all_pages_writeback awaken
periodically, then check the condition.

>
>>                  io_schedule();
>>
>> Signed-off-by: Yunlei He <heyunlei@huawei.com>
>> Signed-off-by: Biao He <hebiao6@huawei.com>
>> ---
>>   fs/f2fs/checkpoint.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
>> index 2bac8a1..f55355d 100644
>> --- a/fs/f2fs/checkpoint.c
>> +++ b/fs/f2fs/checkpoint.c
>> @@ -920,7 +920,7 @@ static void wait_on_all_pages_writeback(struct f2fs_sb_info *sbi)
>>   		if (!get_pages(sbi, F2FS_WRITEBACK))
>>   			break;
>>
>> -		io_schedule();
>> +		io_schedule_timeout(5*HZ);
>>   	}
>>   	finish_wait(&sbi->cp_wait, &wait);
>>   }
>> --
>> 1.9.1
>
>
>
> .
>


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

  reply	other threads:[~2016-02-23  7:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  4:07 [PATCH] f2fs: avoid hungtask problem caused by losing wake_up Yunlei He
2016-02-23  5:44 ` Chao Yu
2016-02-23  7:02   ` He YunLei [this message]
2016-02-23  9:15     ` Chao Yu
2016-02-23 11:36       ` He YunLei
2016-02-24  3:46         ` Chao Yu
2016-02-24  7:32           ` He YunLei
2016-02-24  8:05             ` Chao Yu
2016-02-24  9:45               ` hebiao (G)
2016-02-25  9:32                 ` Chao Yu
2016-02-25  7:36           ` He YunLei
2016-02-25  9:41             ` Chao Yu
2016-02-25 19:03               ` Jaegeuk Kim
2016-02-26  1:15                 ` Chao Yu
2016-02-23  9:32     ` Shawn Lin
2016-02-23 11:45       ` He YunLei

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=56CC0410.50103@huawei.com \
    --to=heyunlei@huawei.com \
    --cc=chao2.yu@samsung.com \
    --cc=hebiao6@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).