[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZFGdob9PRHSR-6ff@codewreck.org>
Date: Wed, 3 May 2023 08:32:49 +0900
From: Dominique Martinet <asmadeus@...ewreck.org>
To: Simon Horman <simon.horman@...igine.com>
Cc: Eric Van Hensbergen <ericvh@...il.com>,
Latchesar Ionkov <lucho@...kov.net>,
Christian Schoenebeck <linux_oss@...debyte.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
v9fs@...ts.linux.dev, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 1/5] 9p: fix ignored return value in v9fs_dir_release
Thanks for all the reviews!
Simon Horman wrote on Tue, May 02, 2023 at 04:46:17PM +0200:
> On Thu, Apr 27, 2023 at 08:23:34PM +0900, Dominique Martinet wrote:
> > retval from filemap_fdatawrite was immediately overwritten by the
> > following p9_fid_put: preserve any error in fdatawrite if there
> > was any first.
> >
> > This fixes the following scan-build warning:
> > fs/9p/vfs_dir.c:220:4: warning: Value stored to 'retval' is never read [deadcode.DeadStores]
> > retval = filemap_fdatawrite(inode->i_mapping);
> > ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Perhaps:
>
> Fixes: 89c58cb395ec ("fs/9p: fix error reporting in v9fs_dir_release")
Right, this one warrants a fix tag as it's the only real bug in this
series.
I'll add the Fixes and fix the typo in patch 5 and send a v2 later
today.
--
Dominique Martinet | Asmadeus
Powered by blists - more mailing lists