From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 349CCEE6440 for ; Fri, 15 Sep 2023 08:23:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232904AbjIOIXj (ORCPT ); Fri, 15 Sep 2023 04:23:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38890 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232242AbjIOIXh (ORCPT ); Fri, 15 Sep 2023 04:23:37 -0400 Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EE05C4C1E; Fri, 15 Sep 2023 01:21:54 -0700 (PDT) Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4Rn6Zs1GXWz8XrRV; Fri, 15 Sep 2023 16:20:53 +0800 (CST) Received: from szxlzmapp01.zte.com.cn ([10.5.231.85]) by mse-fl2.zte.com.cn with SMTP id 38F8KfxW021903; Fri, 15 Sep 2023 16:20:41 +0800 (+08) (envelope-from cheng.lin130@zte.com.cn) Received: from mapi (szxlzmapp07[null]) by mapi (Zmail) with MAPI id mid14; Fri, 15 Sep 2023 16:20:43 +0800 (CST) Date: Fri, 15 Sep 2023 16:20:43 +0800 (CST) X-Zmail-TransId: 2b09650413db226-51e14 X-Mailer: Zmail v1.0 Message-ID: <202309151620439011387@zte.com.cn> In-Reply-To: References: 202309131744458239465@zte.com.cn,ZQJIyx419cw24ppF@dread.disaster.area Mime-Version: 1.0 From: To: Cc: , , , , , Subject: =?UTF-8?B?UmU6IFtQQVRDSCB2M10geGZzOiBpbnRyb2R1Y2UgcHJvdGVjdGlvbiBmb3IgZHJvcCBubGluaw==?= Content-Type: text/plain; charset="UTF-8" X-MAIL: mse-fl2.zte.com.cn 38F8KfxW021903 X-Fangmail-Gw-Spam-Type: 0 X-Fangmail-Anti-Spam-Filtered: true X-Fangmail-MID-QID: 650413E5.001/4Rn6Zs1GXWz8XrRV Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Wed, Sep 13, 2023 at 05:44:45PM +0800, cheng.lin130@zte.com.cn wrote: > > From: Cheng Lin > > > > When abnormal drop_nlink are detected on the inode, > > shutdown filesystem, to avoid corruption propagation. > > > > Signed-off-by: Cheng Lin > > --- > > fs/xfs/xfs_inode.c | 9 +++++++++ > > 1 file changed, 9 insertions(+) > > > > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c > > index 9e62cc500..40cc106ae 100644 > > --- a/fs/xfs/xfs_inode.c > > +++ b/fs/xfs/xfs_inode.c > > @@ -919,6 +919,15 @@ xfs_droplink( > > xfs_trans_t *tp, > > xfs_inode_t *ip) > > { > > + > > + if (VFS_I(ip)->i_nlink == 0) { > > + xfs_alert(ip->i_mount, > > + "%s: Deleting inode %llu with no links.", > > + __func__, ip->i_ino); > > + tp->t_flags |= XFS_TRANS_DIRTY; > Marking the transaction dirty is not necessary. > Otherwise this seems fine. I found the transaction maybe not dirty at this point. Dirty the transaction can make sure to shutdown fs in subsequent xfs_trans_cancel().