linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jan Kara <jack@suse.cz>
Cc: Ted Tso <tytso@mit.edu>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RESEND] mm: Remove false WARN_ON from pagecache_isize_extended()
Date: Wed, 29 Oct 2014 08:26:39 +1100	[thread overview]
Message-ID: <20141028212639.GD16186@dastard> (raw)
In-Reply-To: <1414403885-16219-1-git-send-email-jack@suse.cz>

On Mon, Oct 27, 2014 at 10:58:05AM +0100, Jan Kara wrote:
> The WARN_ON checking whether i_mutex is held in
> pagecache_isize_extended() was wrong because some filesystems (e.g.
> XFS) use different locks for serialization of truncates / writes. So
> just remove the check.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
>  mm/truncate.c | 1 -
>  1 file changed, 1 deletion(-)
> 
>   Ted can you please merge this patch? I originally sent this patch in a
> reply to Fengguangs report and apparently you missed it. Thanks!
> 
> diff --git a/mm/truncate.c b/mm/truncate.c
> index 261eaf6e5a19..c646084e5eec 100644
> --- a/mm/truncate.c
> +++ b/mm/truncate.c
> @@ -755,7 +755,6 @@ void pagecache_isize_extended(struct inode *inode, loff_t from, loff_t to)
>  	struct page *page;
>  	pgoff_t index;
>  
> -	WARN_ON(!mutex_is_locked(&inode->i_mutex));
>  	WARN_ON(to > inode->i_size);
>  
>  	if (from >= to || bsize == PAGE_CACHE_SIZE)

Jan, I'm going to pull this through the XFS tree seeing as nobody
else seems to care about it. Should be upstream by the end of the
week.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2014-10-28 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:58 [PATCH RESEND] mm: Remove false WARN_ON from pagecache_isize_extended() Jan Kara
2014-10-28 21:26 ` Dave Chinner [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=20141028212639.GD16186@dastard \
    --to=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).