From: Larry Woodman <lwoodman@redhat.com>
To: Rik van Riel <riel@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, jmoyer@redhat.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH] do_generic_file_read: clear page errors when issuing a fresh read of the page
Date: Wed, 26 May 2010 12:02:52 -0400 [thread overview]
Message-ID: <1274889772.20515.103.camel@dhcp-100-19-198.bos.redhat.com> (raw)
In-Reply-To: <20100526114940.49f51028@annuminas.surriel.com>
On Wed, 2010-05-26 at 11:49 -0400, Rik van Riel wrote:
> From: Jeff Moyer <jmoyer@redhat.com>
>
> I/O errors can happen due to temporary failures, like multipath
> errors or losing network contact with the iSCSI server. Because
> of that, the VM will retry readpage on the page.
>
> However, do_generic_file_read does not clear PG_error. This
> causes the system to be unable to actually use the data in the
> page cache page, even if the subsequent readpage completes
> successfully!
>
> The function filemap_fault has had a ClearPageError before
> readpage forever. This patch simply adds the same to
> do_generic_file_read.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
> Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
> ---
> mm/filemap.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> Index: linux-2.6.34/mm/filemap.c
> ===================================================================
> --- linux-2.6.34.orig/mm/filemap.c
> +++ linux-2.6.34/mm/filemap.c
> @@ -1106,6 +1106,12 @@ page_not_up_to_date_locked:
> }
>
> readpage:
> + /*
> + * A previous I/O error may have been due to temporary
> + * failures, eg. multipath errors.
> + * PG_error will be set again if readpage fails.
> + */
> + ClearPageError(page);
> /* Start the actual read. The read will unlock the page. */
> error = mapping->a_ops->readpage(filp, page);
>
Acked-by: Larry Woodman <lwoodman@redhat.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-05-26 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 15:49 [PATCH] do_generic_file_read: clear page errors when issuing a fresh read of the page Rik van Riel
2010-05-26 16:02 ` Larry Woodman [this message]
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=1274889772.20515.103.camel@dhcp-100-19-198.bos.redhat.com \
--to=lwoodman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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).