From: Federico Cuello <fedux@lugmen.org.ar>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
linux-kernel@vger.kernel.org
Subject: Re: sync-Regression in 2.6.28.2?
Date: Wed, 04 Feb 2009 15:31:00 -0200 [thread overview]
Message-ID: <4989D0D4.80300@lugmen.org.ar> (raw)
In-Reply-To: <200902041717.27320.nickpiggin@yahoo.com.au>
Nick Piggin wrote:
> [...]
> Thanks, could you reply-to-all when replying to retain ccs please?
>
> Common theme is ext4, which uses no_nrwrite_index_update, and I introduced
> a bug in there which could possibly cause ext4 to go into a loop...
>
> Would it be possible if you can test the following patch?
>
I'll test it as soon as I get home.
Meanwhile, I think the new patch may be slightly wrong. If I understand
correctly PageWriteback(page) is called before nr_to_write is tested for
being > 0 and then decremented if true, but "done" is not set to 1
until the next iteration. So another call to PageWriteback(page) while
take place and then "done" will be set to true (if wbc->sync_mode ==
WB_SYNC_NONE).
If nr_to_write == 1 at the beginning of the loop then two pages will be
written.
I think the test condition should something like:
if (--nr_to_write <= 0 && wbc->sync_mode == WB_SYNC_NONE) {
done = 1;
break;
}
.
.
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Acked-by: Nick Piggin <npiggin@suse.de>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
> mm/page-writeback.c | 21 +++++++++++++++------
> 1 files changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> index b493db7..dc32dae 100644
> --- a/mm/page-writeback.c
> +++ b/mm/page-writeback.c
> @@ -1051,13 +1051,22 @@ continue_unlock:
> }
> }
>
> - if (wbc->sync_mode == WB_SYNC_NONE) {
> - wbc->nr_to_write--;
> - if (wbc->nr_to_write <= 0) {
> - done = 1;
> - break;
> - }
> + if (nr_to_write > 0)
> + nr_to_write--;
> + else if (wbc->sync_mode == WB_SYNC_NONE) {
> + /*
> + * We stop writing back only if we are not
> + * doing integrity sync. In case of integrity
> + * sync we have to keep going because someone
> + * may be concurrently dirtying pages, and we
> + * might have synced a lot of newly appeared
> + * dirty pages, but have not synced all of the
> + * old dirty pages.
> + */
> + done = 1;
> + break;
> }
> +
> if (wbc->nonblocking && bdi_write_congested(bdi)) {
> wbc->encountered_congestion = 1;
> done = 1;
>
next prev parent reply other threads:[~2009-02-04 17:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 9:35 sync-Regression in 2.6.28.2? Ralf Hildebrandt
2009-01-27 21:09 ` Federico Cuello
2009-02-03 1:09 ` Nick Piggin
2009-02-03 19:51 ` Federico Cuello
2009-02-04 6:17 ` Nick Piggin
2009-02-04 17:31 ` Federico Cuello [this message]
2009-02-05 3:25 ` Nick Piggin
2009-02-05 11:54 ` Federico Cuello
2009-02-09 13:45 ` Nick Piggin
2009-02-09 13:49 ` Ralf Hildebrandt
2009-02-15 13:42 ` Ralf Hildebrandt
2009-02-17 4:17 ` Nick Piggin
2009-02-17 15:15 ` Ralf Hildebrandt
2009-02-05 10:19 ` Ralf Hildebrandt
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=4989D0D4.80300@lugmen.org.ar \
--to=fedux@lugmen.org.ar \
--cc=Artem.Bityutskiy@nokia.com \
--cc=Ralf.Hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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