From: Andreas Hindborg <nmi@metaspace.dk>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-fsdevel@vger.kernel.org (open list:ZONEFS FILESYSTEM),
gost.dev@samsung.com, Andreas Hindborg <a.hindborg@samsung.com>,
Naohiro Aota <naohiro.aota@wdc.com>,
Johannes Thumshirn <jth@kernel.org>,
linux-kernel@vger.kernel.org (open list),
"Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
Subject: [PATCH] zonefs: do not use append if device does not support it
Date: Mon, 26 Jun 2023 18:47:52 +0200 [thread overview]
Message-ID: <20230626164752.1098394-1-nmi@metaspace.dk> (raw)
From: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
Zonefs will try to use `zonefs_file_dio_append()` for direct sync writes even if
device `max_zone_append_sectors` is zero. This will cause the IO to fail as the
io vector is truncated to zero. It also causes a call to
`invalidate_inode_pages2_range()` with end set to UINT_MAX, which is probably
not intentional. Thus, do not use append when device does not support it.
Signed-off-by: Andreas Hindborg (Samsung) <nmi@metaspace.dk>
---
fs/zonefs/file.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/zonefs/file.c b/fs/zonefs/file.c
index 132f01d3461f..c97fe2aa20b0 100644
--- a/fs/zonefs/file.c
+++ b/fs/zonefs/file.c
@@ -536,9 +536,11 @@ static ssize_t zonefs_write_checks(struct kiocb *iocb, struct iov_iter *from)
static ssize_t zonefs_file_dio_write(struct kiocb *iocb, struct iov_iter *from)
{
struct inode *inode = file_inode(iocb->ki_filp);
+ struct block_device *bdev = inode->i_sb->s_bdev;
struct zonefs_inode_info *zi = ZONEFS_I(inode);
struct zonefs_zone *z = zonefs_inode_zone(inode);
struct super_block *sb = inode->i_sb;
+ unsigned int max_append = bdev_max_zone_append_sectors(bdev);
bool sync = is_sync_kiocb(iocb);
bool append = false;
ssize_t ret, count;
@@ -581,7 +583,7 @@ static ssize_t zonefs_file_dio_write(struct kiocb *iocb, struct iov_iter *from)
append = sync;
}
- if (append) {
+ if (append && max_append) {
ret = zonefs_file_dio_append(iocb, from);
} else {
/*
base-commit: 45a3e24f65e90a047bef86f927ebdc4c710edaa1
--
2.41.0
next reply other threads:[~2023-06-26 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 16:47 Andreas Hindborg [this message]
2023-06-26 17:54 ` Johannes Thumshirn
2023-06-26 18:23 ` Andreas Hindborg (Samsung)
2023-06-27 0:21 ` Damien Le Moal
2023-06-27 5:45 ` Andreas Hindborg (Samsung)
2023-06-27 3:45 ` Christoph Hellwig
2023-06-27 4:45 ` Damien Le Moal
2023-06-27 4:48 ` Christoph Hellwig
2023-06-27 4:50 ` Damien Le Moal
2023-06-27 5:14 ` Andreas Hindborg (Samsung)
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=20230626164752.1098394-1-nmi@metaspace.dk \
--to=nmi@metaspace.dk \
--cc=a.hindborg@samsung.com \
--cc=dlemoal@kernel.org \
--cc=gost.dev@samsung.com \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naohiro.aota@wdc.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
all inboxes | Powered by JetHome®