From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] ext4: Fix mmap data corruption when blocksize < pagesize
Date: Wed, 1 Oct 2014 22:06:33 -0400 [thread overview]
Message-ID: <20141002020633.GB16766@thunk.org> (raw)
In-Reply-To: <1411648916-16773-3-git-send-email-jack@suse.cz>
On Thu, Sep 25, 2014 at 02:41:56PM +0200, Jan Kara wrote:
> Use truncate_isize_extended() when hole is being created in a file so that
> ->page_mkwrite() will get called for the partial tail page if it is
> mmaped (see the first patch in the series for details).
>
> Signed-off-by: Jan Kara <jack@suse.cz>
Applied to the ext4 tree, thanks.
- Ted
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-02 2:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 12:41 [PATCH 0/2 v2] Fix data corruption when blocksize < pagesize for mmapped data Jan Kara
2014-09-25 12:41 ` [PATCH 1/2] vfs: Fix data corruption when blocksize < pagesize for mmaped data Jan Kara
2014-09-25 12:41 ` Jan Kara
2014-10-02 2:06 ` Theodore Ts'o
2014-10-02 2:06 ` Theodore Ts'o
2014-09-25 12:41 ` [PATCH 2/2] ext4: Fix mmap data corruption when blocksize < pagesize Jan Kara
2014-09-25 12:41 ` Jan Kara
2014-10-02 2:06 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-10 14:23 [Cluster-devel] [PATCH 0/2 v2] Fix data corruption when blocksize < pagesize for mmapped data Jan Kara
2014-10-10 14:23 ` [PATCH 2/2] ext4: Fix mmap data corruption when blocksize < pagesize Jan Kara
2014-10-10 14:23 ` Jan Kara
2014-09-23 15:03 [PATCH 0/2] Fix " Jan Kara
2014-09-23 15:03 ` [PATCH 2/2] ext4: Fix mmap " Jan Kara
2014-09-24 8:45 ` Jan Kara
2014-09-24 8:45 ` Jan Kara
2014-09-24 8:57 ` Jan Kara
2014-09-24 8:57 ` Jan Kara
2014-09-24 8:57 ` Jan Kara
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=20141002020633.GB16766@thunk.org \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.