[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220821233251.GI3600936@dread.disaster.area>
Date: Mon, 22 Aug 2022 09:32:51 +1000
From: Dave Chinner <david@...morbit.com>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Shiyang Ruan <ruansy.fnst@...itsu.com>,
Dan Williams <dan.j.williams@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
"nvdimm@...ts.linux.dev" <nvdimm@...ts.linux.dev>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"hch@...radead.org" <hch@...radead.org>,
"jane.chu@...cle.com" <jane.chu@...cle.com>
Subject: Re: [PATCH] xfs: on memory failure, only shut down fs after scanning
all mappings
On Thu, Aug 18, 2022 at 10:00:17AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@...nel.org>
>
> xfs_dax_failure_fn is used to scan the filesystem during a memory
> failure event to look for memory mappings to revoke. Unfortunately, if
> it encounters an rmap record for filesystem metadata, it will shut down
> the filesystem and the scan immediately. This means that we don't
> complete the mapping revocation scan and instead leave live mappings to
> failed memory. Fix the function to defer the shutdown until after we've
> finished culling mappings.
>
> While we're at it, add the usual "xfs_" prefix to struct failure_info,
> and actually initialize mf_flags.
>
> Signed-off-by: Darrick J. Wong <djwong@...nel.org>
Looks fine.
Reviewed-by: Dave Chinner <dchinner@...hat.com>
--
Dave Chinner
david@...morbit.com
Powered by blists - more mailing lists