Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp937016pxb; Wed, 27 Oct 2021 15:36:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzgsRBfcRQ8PC/sPKDY6t37rvOUvAeOjBGt3QhtO2zmPZE0xlKdQBzl7U4KSU5U6B7qSzjU X-Received: by 2002:a05:6a00:2283:b0:47c:494:1177 with SMTP id f3-20020a056a00228300b0047c04941177mr440995pfe.69.1635374200216; Wed, 27 Oct 2021 15:36:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635374200; cv=none; d=google.com; s=arc-20160816; b=SbaT8dbUbERLLXvn+mUaYQBsim/abxtiYFaypXSc/4GwdRsRFSMrbYSSkIKuHIGTn0 Ch14CBonfhQCcB+bWrjalxHeovI0USOXmlGke7gHgu45QYauMASoZ+DJiLlpiZpfEACy thlqBFEKnoWPkGIpMbZ0rYxhb9EounERzDif/Hne4GiqtV4hotpoVjsqyGJPGcqYcsyk SyP2j97y0Vl95ispxw/N0B6bjSsoDrWccBGnbxLBn5IfqCYUFzwgvXPaNehsDjUqh4vY VTV5nOx5nv6yHgHnKySWzaYO40kPPRmdjyNSDSxqdJkb5+F0yirWFGYkH4yxJyx8y8O6 Clgg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=iWF/YNor2JSMnupn32Wk/02g21ycx7A3oYTrbqnUVdY=; b=WoqlwBviShyUDsgANRqgs917noydxha3x+Sf1aN7NRM79fdF0zGBw3Kd7SZyJlAUz0 Tpg9Mufva0/EnDKPyCtUoASJUh+Bk5f1OnVoJBfc12WtPB965vm51Q+gNY2z1v+xjAWB HDA6ms1cRbIgojtABSr3bai8j4nURuvWDYgHoMBWn2qKeudpCjcOvOkUTv0mZLenV9+h 0SZMMkxNUh3MqvF2cA1ay4m2kytCokONtCKdeDzB9563YIHzOtkQLKBFdTxRERu/Pb0z 8ALG5flOxA3xxqi/SXZIQDn6fauP6FkI8AL2R4iYpRiQa43A0sgSRuPsCJMlrpwrsmbE vKfA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=d1nbimgn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y2si1663804pfi.26.2021.10.27.15.36.27; Wed, 27 Oct 2021 15:36:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=d1nbimgn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229723AbhJ0Wgs (ORCPT + 99 others); Wed, 27 Oct 2021 18:36:48 -0400 Received: from mail.kernel.org ([198.145.29.99]:53742 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229505AbhJ0Wgr (ORCPT ); Wed, 27 Oct 2021 18:36:47 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id B4A7060EBD; Wed, 27 Oct 2021 22:34:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1635374061; bh=4SqiEoUxJz4vtG++4/zpHHHXF6cTsG3IDqC+tBAV7BE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=d1nbimgnUwu6ytcWSdSaArsq65+JkZFDoLif7EkFAQ8WHU3MX54WUEux3Av50svpQ wf4w1OqedzwetZ8vWSbmM1EduhPPR0TATul/CtZEV660GawZFZ46RkApwjRxwDrG96 ihV7BTLZt6eEaHegdcKQbZsuajei28HAsHsdWD4/cWz8ZrX63wlw06lknPPRqsgXNn H23kwiDxVpRGt+sFIFXbxVLC8VIrEykXvp9ocBS/vH3OQMikto3PBcVBWe91gImCWi ChgBlLlCx1zo9my4ngeFNFoEjVBO8dVeS1lwwbDmPuU66fW/Xz8lCw7rOlpQoRhhe3 GxciBF6wlzCNQ== Date: Wed, 27 Oct 2021 15:34:20 -0700 From: Jaegeuk Kim To: Chao Yu Cc: Pavel Machek , linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [PATCH] f2fs: fix incorrect return value in f2fs_sanity_check_ckpt() Message-ID: References: <20210922152705.720071-1-chao@kernel.org> <20210924095021.GA16651@duo.ucw.cz> <4897a06a-9f9e-27ce-91d3-58721bee42ac@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4897a06a-9f9e-27ce-91d3-58721bee42ac@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Could you post the patch again? I don't see this in my box. On 10/27, Chao Yu wrote: > Jaegeuk, > > Missed to apply this patch? > > Thanks, > > On 2021/9/24 17:50, Pavel Machek wrote: > > Hi! > > > > > This code looks quite confused: part of function returns 1 on > > > corruption, part returns -errno. The problem is not stable-specific. > > > > > > [1] https://lkml.org/lkml/2021/9/19/207 > > > > > > Let's fix to make 'insane cp_payload case' to return 1 rater than > > > EFSCORRUPTED, so that return value can be kept consistent for all > > > error cases, it can avoid confusion of code logic. > > > > > > Fixes: 65ddf6564843 ("f2fs: fix to do sanity check for sb/cp fields correctly") > > > Reported-by: Pavel Machek > > > Signed-off-by: Chao Yu > > > > Reviewed-by: Pavel Machek > > > > (This is good minimal fix, but eventually I believe the function > > should switch to 0/-errno... for consistency with rest of kernel). > > > > Thank you, > > Pavel > > > > > +++ b/fs/f2fs/super.c > > > @@ -3487,7 +3487,7 @@ int f2fs_sanity_check_ckpt(struct f2fs_sb_info *sbi) > > > NR_CURSEG_PERSIST_TYPE + nat_bits_blocks >= blocks_per_seg)) { > > > f2fs_warn(sbi, "Insane cp_payload: %u, nat_bits_blocks: %u)", > > > cp_payload, nat_bits_blocks); > > > - return -EFSCORRUPTED; > > > + return 1; > > > } > > > if (unlikely(f2fs_cp_error(sbi))) { > >