From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: linux-fsdevel@vger.kernel.org
Cc: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Hans Holmberg <hans.holmberg@wdc.com>,
Christoph Hellwig <hch@lst.de>
Subject: [PATCH v2 0/2] zonefs: Fix data corruption and error return
Date: Thu, 30 Mar 2023 10:54:21 +0900 [thread overview]
Message-ID: <20230330015423.2170293-1-damien.lemoal@opensource.wdc.com> (raw)
Patch 1 fixes a potential data corruption when the last page of the
inode is cached and a sync append direct write partially modify the
data of that page on disk. The second patch avoids propagating to user
space the -ENOTBLK error potentially returned by iomap_dio_rw().
Changes from v1:
- Reworked patch 1 commit message and use an exact end argument for the
call to invalidate_inode_pages2_range().
- Added patch 2.
Damien Le Moal (2):
zonefs: Always invalidate last cached page on append write
zonefs: Do not propagate iomap_dio_rw() ENOTBLK error to user space
fs/zonefs/file.c | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-30 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 1:54 Damien Le Moal [this message]
2023-03-30 1:54 ` [PATCH v2 1/2] zonefs: Always invalidate last cached page on append write Damien Le Moal
2023-03-30 1:58 ` Christoph Hellwig
2023-03-30 1:54 ` [PATCH v2 2/2] zonefs: Do not propagate iomap_dio_rw() ENOTBLK error to user space Damien Le Moal
2023-03-30 1:58 ` Christoph Hellwig
2023-03-30 8:45 ` [PATCH v2 0/2] zonefs: Fix data corruption and error return Johannes Thumshirn
2023-03-30 11:25 ` Hans Holmberg
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=20230330015423.2170293-1-damien.lemoal@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=hans.holmberg@wdc.com \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).