From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DD46E2C99 for ; Mon, 13 Dec 2021 07:38:18 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id CD55C68AA6; Mon, 13 Dec 2021 08:38:08 +0100 (CET) Date: Mon, 13 Dec 2021 08:38:08 +0100 From: Christoph Hellwig To: Matthew Wilcox Cc: Christoph Hellwig , dan.j.williams@intel.com, linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev, Dan Carpenter Subject: Re: [PATCH] iomap: turn the byte variable in iomap_zero_iter into a ssize_t Message-ID: <20211213073808.GA20684@lst.de> References: <20211208091203.2927754-1-hch@lst.de> Precedence: bulk X-Mailing-List: nvdimm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) On Sat, Dec 11, 2021 at 05:50:51PM +0000, Matthew Wilcox wrote: > 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) Indeed. It might make sense to eventually switch to actually return an errno or a bool as the current calling convention is rather confusing.