From: Carlos Maiolino <cmaiolino@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: Fix WARN_ON(delalloc) in xfs_vm_releasepage()
Date: Thu, 14 Mar 2013 17:21:09 -0300 [thread overview]
Message-ID: <20130314202108.GB32283@andromeda.usersys.redhat.com> (raw)
In-Reply-To: <1363267854-25602-1-git-send-email-jack@suse.cz>
On Thu, Mar 14, 2013 at 02:30:54PM +0100, Jan Kara wrote:
> When a dirty page is truncated from a file but reclaim gets to it before
> truncate_inode_pages(), we hit WARN_ON(delalloc) in
> xfs_vm_releasepage(). This is because reclaim tries to write the page,
> xfs_vm_writepage() just bails out (leaving page clean) and thus reclaim
> thinks it can continue and calls xfs_vm_releasepage() on page with dirty
> buffers.
>
> Fix the issue by redirtying the page in xfs_vm_writepage(). This makes
> reclaim stop reclaiming the page and also logically it keeps page in a
> more consistent state where page with dirty buffers has PageDirty set.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> fs/xfs/xfs_aops.c | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 5f707e5..3244c98 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -953,13 +953,13 @@ xfs_vm_writepage(
> unsigned offset_into_page = offset & (PAGE_CACHE_SIZE - 1);
>
> /*
> - * Just skip the page if it is fully outside i_size, e.g. due
> - * to a truncate operation that is in progress.
> + * Skip the page if it is fully outside i_size, e.g. due to a
> + * truncate operation that is in progress. We must redirty the
> + * page so that reclaim stops reclaiming it. Otherwise
> + * xfs_vm_releasepage() is called on it and gets confused.
> */
> - if (page->index >= end_index + 1 || offset_into_page == 0) {
> - unlock_page(page);
> - return 0;
> - }
> + if (page->index >= end_index + 1 || offset_into_page == 0)
> + goto redirty;
>
> /*
> * The page straddles i_size. It must be zeroed out on each
> --
> 1.7.1
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
Looks Good,
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-14 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 13:30 [PATCH] xfs: Fix WARN_ON(delalloc) in xfs_vm_releasepage() Jan Kara
2013-03-14 20:21 ` Carlos Maiolino [this message]
2013-03-15 20:52 ` Ben Myers
2013-03-18 16:05 ` Jan Kara
2013-03-19 3:47 ` Dave Chinner
2013-03-19 15:42 ` Jan Kara
2013-03-21 1:37 ` Dave Chinner
2013-03-22 21:12 ` Ben Myers
2013-03-16 7:35 ` Dave Chinner
2013-03-22 23:18 ` Ben Myers
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=20130314202108.GB32283@andromeda.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=jack@suse.cz \
--cc=xfs@oss.sgi.com \
/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