From: Matthew Wilcox <willy@infradead.org>
To: Christoph Hellwig <hch@lst.de>
Cc: dan.j.williams@intel.com, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] iomap: turn the byte variable in iomap_zero_iter into a ssize_t
Date: Sat, 11 Dec 2021 17:50:51 +0000 [thread overview]
Message-ID: <YbTk+1I4VFQpgjM/@casper.infradead.org> (raw)
In-Reply-To: <20211208091203.2927754-1-hch@lst.de>
On Wed, Dec 08, 2021 at 10:12:03AM +0100, Christoph Hellwig wrote:
> bytes also hold the return value from iomap_write_end, which can contain
> a negative error value. As bytes is always less than the page size even
> the signed type can hold the entire possible range.
iomap_write_end() can't return an errno. I went through and checked as
part of the folio conversion. It actually has two return values -- 0
on error and 'len' on success. And it can't have an error because
that only occurs if 'copied' is less than 'length'.
So I think this should actually be:
- bytes = iomap_write_end(iter, pos, bytes, bytes, folio);
- if (bytes < 0)
- return bytes;
+ status = iomap_write_end(iter, pos, bytes, bytes, folio);
+ if (WARN_ON_ONCE(status == 0))
+ return -EIO;
just like its counterpart loop in iomap_unshare_iter()
(ok this won't apply to Dan's tree, but YKWIM)
next prev parent reply other threads:[~2021-12-11 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 9:12 [PATCH] iomap: turn the byte variable in iomap_zero_iter into a ssize_t Christoph Hellwig
2021-12-09 0:48 ` Darrick J. Wong
2021-12-09 0:55 ` Darrick J. Wong
2021-12-09 1:58 ` Dan Williams
2021-12-09 6:11 ` Christoph Hellwig
2021-12-09 18:19 ` Darrick J. Wong
2021-12-11 17:50 ` Matthew Wilcox [this message]
2021-12-13 7:38 ` Christoph Hellwig
2021-12-20 22:10 ` Matthew Wilcox
2021-12-21 4:12 ` Dan Williams
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=YbTk+1I4VFQpgjM/@casper.infradead.org \
--to=willy@infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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).