[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWWii6HhlfkWXSq8@infradead.org>
Date: Tue, 28 Nov 2023 00:19:23 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Jiachen Zhang <zhangjiachen.jaycee@...edance.com>
Cc: Chandan Babu R <chandan.babu@...cle.com>,
"Darrick J. Wong" <djwong@...nel.org>,
Dave Chinner <dchinner@...hat.com>,
Allison Henderson <allison.henderson@...cle.com>,
Zhang Tianci <zhangtianci.1997@...edance.com>,
Brian Foster <bfoster@...hat.com>, Ben Myers <bpm@....com>,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org,
xieyongji@...edance.com, me@...x.top
Subject: Re: [PATCH 1/2] xfs: ensure tmp_logflags is initialized in
xfs_bmap_del_extent_real
On Tue, Nov 28, 2023 at 01:32:01PM +0800, Jiachen Zhang wrote:
> In the case of returning -ENOSPC, ensure tmp_logflags is initialized by 0.
> Otherwise the caller __xfs_bunmapi will set uninitialized illegal
> tmp_logflags value into xfs log, which might cause unpredictable error
> in the log recovery procedure.
This looks good:
Reviewed-by: Christoph Hellwig <hch@....de>
But I wonder if removing the local flags variable and always directly
assigning to *logflagsp might be more robust in the long run.
Powered by blists - more mailing lists