From: Josef Bacik <jbacik@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: trond.myklebust@fys.uio.no, npiggin@suse.de,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: NFS infinite loop in filemap_fault()
Date: Thu, 8 May 2008 09:07:59 -0400 [thread overview]
Message-ID: <20080508130759.GA30499@unused.rdu.redhat.com> (raw)
In-Reply-To: <E1JtzuH-0006nY-AM@pomaz-ex.szeredi.hu>
On Thu, May 08, 2008 at 08:47:09AM +0200, Miklos Szeredi wrote:
> > Page fault on NFS apparently goes into an infinite loop if the read on
> > the server fails.
> >
> > I don't understand the NFS readpage code, but the filemap_fault() code
> > looks somewhat suspicious:
> >
> > /*
> > * Umm, take care of errors if the page isn't up-to-date.
> > * Try to re-read it _once_. We do this synchronously,
> > * because there really aren't any performance issues here
> > * and we need to check for errors.
> > */
> > ClearPageError(page);
> > error = mapping->a_ops->readpage(file, page);
> > page_cache_release(page);
> >
> > if (!error || error == AOP_TRUNCATED_PAGE)
> > goto retry_find;
> >
> > The comment doesn't seem to match what the it actually does: if
> > ->readpage() is asynchronous, then this will just repeat everything,
> > without any guarantee that it will re-read once.
>
> This patch fixes it. It's probably wrong in some subtle way though...
>
> Miklos
>
>
> ---
> mm/filemap.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> Index: linux.git/mm/filemap.c
> ===================================================================
> --- linux.git.orig/mm/filemap.c 2008-05-08 08:17:22.000000000 +0200
> +++ linux.git/mm/filemap.c 2008-05-08 08:19:59.000000000 +0200
> @@ -1461,6 +1461,12 @@ page_not_uptodate:
> */
> ClearPageError(page);
> error = mapping->a_ops->readpage(file, page);
> + if (!error && !PageUptodate(page)) {
Shouldn't you have (!error || error != AOP_TRUNCATED_PAGE), since the fs can
return AOP_TRUNCATED_PAGE if it needs vfs to try the readpage again? Things
like OCFS2/GFS2 do this, they send of a lock request and return
AOP_TRUNCATED_PAGE so that when we come back into readpage we are already
holding our lock without blocking while holding the page lock. Thanks,
Josef
--
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>
next prev parent reply other threads:[~2008-05-08 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JtqLW-0005j5-KU@pomaz-ex.szeredi.hu>
2008-05-08 6:47 ` Miklos Szeredi
2008-05-08 13:07 ` Josef Bacik [this message]
2008-05-08 18:42 ` Miklos Szeredi
2008-05-08 18:29 ` Josef Bacik
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=20080508130759.GA30499@unused.rdu.redhat.com \
--to=jbacik@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--cc=npiggin@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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