linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Evgeniy Dushistov <dushistov@mail.ru>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH]: ufs: ufs_get_locked_patch race fix
Date: Mon, 31 Jul 2006 23:02:51 -0700	[thread overview]
Message-ID: <20060731230251.3b149902.akpm@osdl.org> (raw)
In-Reply-To: <20060731125702.GA5094@rain>

On Mon, 31 Jul 2006 16:57:02 +0400
Evgeniy Dushistov <dushistov@mail.ru> wrote:

> As discussed earlier:
> http://lkml.org/lkml/2006/6/28/136
> this patch fixes such issue:
> `ufs_get_locked_page' takes page from cache
> after that `vmtruncate' takes page and deletes it from cache
> `ufs_get_locked_page' locks page, and reports about EIO error.
> 
> Also because of find_lock_page always return valid page or NULL,
> we have no need check it if page not NULL.
> 
> Signed-off-by: Evgeniy Dushistov <dushistov@mail.ru>
> 
> 
> ---
> 
> 
> Index: linux-2.6.18-rc2-mm1/fs/ufs/util.c
> ===================================================================
> --- linux-2.6.18-rc2-mm1.orig/fs/ufs/util.c
> +++ linux-2.6.18-rc2-mm1/fs/ufs/util.c
> @@ -257,6 +257,7 @@ try_again:
>  		page = read_cache_page(mapping, index,
>  				       (filler_t*)mapping->a_ops->readpage,
>  				       NULL);
> +
>  		if (IS_ERR(page)) {
>  			printk(KERN_ERR "ufs_change_blocknr: "
>  			       "read_cache_page error: ino %lu, index: %lu\n",
> @@ -266,6 +267,13 @@ try_again:
>  
>  		lock_page(page);
>  
> +		if (unlikely(page->mapping != mapping ||
> +			     page->index != index)) {
> +			unlock_page(page);
> +			page_cache_release(page);
> +			goto try_again;
> +		}
> +
>  		if (!PageUptodate(page) || PageError(page)) {
>  			unlock_page(page);
>  			page_cache_release(page);

Looks good to me.

Is there any need to be checking ->index?  Normally we simply use the
sequence:

	lock_page(page);
	if (page->mapping == NULL)
		/* truncate got there first */

to handle this case.

  reply	other threads:[~2006-08-01  6:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 12:57 [PATCH]: ufs: ufs_get_locked_patch race fix Evgeniy Dushistov
2006-08-01  6:02 ` Andrew Morton [this message]
2006-08-01  7:18   ` Nick Piggin
2006-08-01  7:30   ` Evgeniy Dushistov
2006-08-01  7:39     ` Andrew Morton
2006-08-01 12:00       ` [PATCH]: ufs: ufs_change_blocknr: skip truncated pages Evgeniy Dushistov

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=20060731230251.3b149902.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=dushistov@mail.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).