From: Peter Lundkvist <p.lundkvist@telia.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org, rjw@sisk.pl
Subject: Re: [PATCH] Page writeback broken after resume: wb_timer lost
Date: Sun, 21 May 2006 08:52:48 +0200 [thread overview]
Message-ID: <20060521065248.GA5659@localhost> (raw)
In-Reply-To: <20060520171244.4399bc54.akpm@osdl.org>
On Sat, May 20, 2006 at 05:12:44PM -0700, Andrew Morton wrote:
>
> Peter, does this fix it?
>
Yes, it does fix the problem.
Hopefully we'll see this fix in the next stable update, because
of the risk of data loss.
>
> From: Andrew Morton <akpm@osdl.org>
>
> pdflush is carefully designed to ensure that all wakeups have some
> corresponding work to do - if a woken-up pdflush thread discovers that it
> hasn't been given any work to do then this is considered an error.
>
> That all broke when swsusp came along - because a timer-delivered wakeup to a
> frozen pdflush thread will just get lost. This causes the pdflush thread to
> get lost as well: the writeback timer is supposed to be re-armed by pdflush in
> process context, but pdflush doesn't execute the callout which does this.
>
> Fix that up by ignoring the return value from try_to_freeze(): jsut proceed,
> see if we have any work pending and only go back to sleep if that is not the
> case.
>
>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
>
> mm/pdflush.c | 9 ++-------
> 1 files changed, 2 insertions(+), 7 deletions(-)
>
> diff -puN mm/pdflush.c~pdflush-handle-resume-wakeups mm/pdflush.c
> --- devel/mm/pdflush.c~pdflush-handle-resume-wakeups 2006-05-20 17:02:21.000000000 -0700
> +++ devel-akpm/mm/pdflush.c 2006-05-20 17:11:25.000000000 -0700
> @@ -104,13 +104,8 @@ static int __pdflush(struct pdflush_work
> list_move(&my_work->list, &pdflush_list);
> my_work->when_i_went_to_sleep = jiffies;
> spin_unlock_irq(&pdflush_lock);
> -
> schedule();
> - if (try_to_freeze()) {
> - spin_lock_irq(&pdflush_lock);
> - continue;
> - }
> -
> + try_to_freeze();
> spin_lock_irq(&pdflush_lock);
> if (!list_empty(&my_work->list)) {
> printk("pdflush: bogus wakeup!\n");
> @@ -118,7 +113,7 @@ static int __pdflush(struct pdflush_work
> continue;
> }
> if (my_work->fn == NULL) {
> - printk("pdflush: NULL work function\n");
> + printk("pflush: resuming\n");
> continue;
> }
> spin_unlock_irq(&pdflush_lock);
> _
>
>
>
next prev parent reply other threads:[~2006-05-21 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 13:03 [PATCH] Page writeback broken after resume: wb_timer lost Peter Lundkvist
2006-05-20 17:37 ` Andrew Morton
2006-05-20 22:50 ` Pavel Machek
2006-05-21 0:12 ` Andrew Morton
2006-05-21 6:52 ` Peter Lundkvist [this message]
2006-05-21 10:08 ` Pavel Machek
2006-06-16 21:24 ` Johannes Stezenbach
2006-06-16 23:12 ` Nigel Cunningham
2006-06-19 15:41 ` Mark Lord
2006-06-21 3:38 ` Mark Lord
2006-06-21 3:54 ` Andrew Morton
2006-06-21 4:10 ` Mark Lord
2006-06-21 4:19 ` Andrew Morton
2006-06-22 20:25 ` Mark Lord
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=20060521065248.GA5659@localhost \
--to=p.lundkvist@telia.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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.