From: Jan Kara <jack@suse.cz>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Jan Kara <jack@suse.cz>, Ted Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Unmap metadata when zeroing blocks
Date: Mon, 3 Oct 2016 09:18:48 +0200 [thread overview]
Message-ID: <20161003071848.GC6457@quack2.suse.cz> (raw)
In-Reply-To: <20160929131457.wyhlp34n55ewzzxu@localhost.localdomain>
Hi,
On Thu 29-09-16 15:14:57, Lukas Czerner wrote:
> do we have a xfstest case for this particular problem ?
Not specifically, but some of the existing xfstests did trigger this
problem for me which is how I found it out...
Honza
> On Tue, Sep 27, 2016 at 06:15:18PM +0200, Jan Kara wrote:
> > When zeroing blocks for DAX allocations, we also have to unmap aliases
> > in the block device mappings. Otherwise writeback can overwrite zeros
> > with stale data from block device page cache.
> >
> > Signed-off-by: Jan Kara <jack@suse.cz>
> > ---
> > fs/ext4/inode.c | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > Ted, can you merge this patch please? It's a data corruption issue for DAX.
> >
> > diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> > index c6ea25a190f8..87150122d361 100644
> > --- a/fs/ext4/inode.c
> > +++ b/fs/ext4/inode.c
> > @@ -647,11 +647,19 @@ found:
> > /*
> > * We have to zeroout blocks before inserting them into extent
> > * status tree. Otherwise someone could look them up there and
> > - * use them before they are really zeroed.
> > + * use them before they are really zeroed. We also have to
> > + * unmap metadata before zeroing as otherwise writeback can
> > + * overwrite zeros with stale data from block device.
> > */
> > if (flags & EXT4_GET_BLOCKS_ZERO &&
> > map->m_flags & EXT4_MAP_MAPPED &&
> > map->m_flags & EXT4_MAP_NEW) {
> > + ext4_lblk_t i;
> > +
> > + for (i = 0; i < map->m_len; i++) {
> > + unmap_underlying_metadata(inode->i_sb->s_bdev,
> > + map->m_pblk + i);
> > + }
> > ret = ext4_issue_zeroout(inode, map->m_lblk,
> > map->m_pblk, map->m_len);
> > if (ret) {
> > --
> > 2.6.6
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-10-03 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:15 [PATCH] ext4: Unmap metadata when zeroing blocks Jan Kara
2016-09-29 13:14 ` Lukas Czerner
2016-10-03 7:18 ` Jan Kara [this message]
2016-09-30 6:03 ` Theodore Ts'o
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=20161003071848.GC6457@quack2.suse.cz \
--to=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@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).