From: yu kuai <yukuai3@huawei.com>
To: <darrick.wong@oracle.com>, <bfoster@redhat.com>,
<dchinner@redhat.com>, <sandeen@sandeen.net>,
<cmaiolino@redhat.com>, <hch@lst.de>
Cc: <linux-xfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yukuai3@huawei.com>, <zhengbin13@huawei.com>,
<yi.zhang@huawei.com>, <houtao1@huawei.com>
Subject: [PATCH 0/2] fix stale data exposure problem
Date: Thu, 26 Dec 2019 21:47:19 +0800 [thread overview]
Message-ID: <20191226134721.43797-1-yukuai3@huawei.com> (raw)
The problem was found by generic/042, however, I have no idea why the
problem didn't get fixed.
yu kuai (2):
xfs: introduce xfs_bmap_split_da_extent
xfs: fix stale data exposure problem when punch hole, collapse range
or zero range across a delalloc extent
fs/xfs/libxfs/xfs_bmap.c | 26 ++++++++++++++++++++--
fs/xfs/libxfs/xfs_bmap.h | 1 +
fs/xfs/xfs_file.c | 47 ++++++++++++++++++++++++++++++++++++++++
3 files changed, 72 insertions(+), 2 deletions(-)
--
2.17.2
next reply other threads:[~2019-12-26 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 13:47 yu kuai [this message]
2019-12-26 13:47 ` [PATCH 1/2] xfs: introduce xfs_bmap_split_da_extent yu kuai
2020-01-05 21:04 ` Dave Chinner
2019-12-26 13:47 ` [PATCH 2/2] xfs: fix stale data exposure problem when punch hole, collapse range or zero range across a delalloc extent yu kuai
2019-12-27 0:17 ` kbuild test robot
2019-12-27 0:17 ` kbuild test robot
2019-12-27 0:17 ` [RFC PATCH] xfs: try_split_da_extent can be static kbuild test robot
2019-12-27 0:17 ` kbuild test robot
2019-12-27 14:25 ` [xfs] 1c6c6a28e3: Assertion_failed kernel test robot
2019-12-27 14:25 ` kernel test robot
2020-01-06 21:57 ` [PATCH 2/2] xfs: fix stale data exposure problem when punch hole, collapse range or zero range across a delalloc extent Darrick J. Wong
2020-01-07 2:09 ` yukuai (C)
2020-01-07 18:17 ` Darrick J. Wong
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=20191226134721.43797-1-yukuai3@huawei.com \
--to=yukuai3@huawei.com \
--cc=bfoster@redhat.com \
--cc=cmaiolino@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=houtao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=yi.zhang@huawei.com \
--cc=zhengbin13@huawei.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.