linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH] ext4: fix mmap data corruption in nodelalloc mode when blocksize < pagesize
Date: Thu, 12 Feb 2015 23:01:33 -0500	[thread overview]
Message-ID: <20150213040133.GC2268@thunk.org> (raw)
In-Reply-To: <1423185183-3032-1-git-send-email-wangxg.fnst@cn.fujitsu.com>

On Fri, Feb 06, 2015 at 09:13:03AM +0800, Xiaoguang Wang wrote:
> Since commit 90a8020 and d6320cb, Jan Kara has fixed this issue partially.
> This mmap data corruption still exists in nodelalloc mode, fix this.
> 
> Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
> Reviewed-by:   Jan Kara <jack@suse.cz>

Applied, thanks.

					- Ted

      reply	other threads:[~2015-02-13  4:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  1:13 [PATCH] ext4: fix mmap data corruption in nodelalloc mode when blocksize < pagesize Xiaoguang Wang
2015-02-13  4:01 ` Theodore Ts'o [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=20150213040133.GC2268@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=wangxg.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).