Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp19627900rwd; Wed, 28 Jun 2023 11:50:20 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5kC+GvdkaWaOOQPiQTODbA1SvvpjDxd23a/FSW6LQIHcBMAboI57rVlRYSXxMuQC8mV1d+ X-Received: by 2002:a05:6402:1208:b0:51d:8075:72ef with SMTP id c8-20020a056402120800b0051d807572efmr8788240edw.7.1687978220495; Wed, 28 Jun 2023 11:50:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687978220; cv=none; d=google.com; s=arc-20160816; b=JWVGEQLAPefhde/RIMeC4N2UY6mQVJUz3CsYA/l6ZSUz80alm5rwmNuoKxWbPj8SIY 8EG94ZKRxY6FqVG476gqLb8p92lpqr5ASSCjD1yVYVICYyWj/Bn1GN3+LsXtDiFH0NZH MgkiBaJwQVMq7mnoGcdH7oJTk5BopI+fqDH/TAGV+raHWFSggKbPElIaJyWwelOUsTtL kLA29Z7gfZul4W1K4fONMovsIX1PMrUSxku9An94mZOCE4qIgyVRgVcfKEVBhRDVUN+k FarZwthLC0ICPPYJgp0NKmbMB44OLJ4eeuk8M5wh+/UZuO40MxdCcgvaziVYEYA41JJZ C5bg== 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=q2bbf57Pb4pvQcTv4CjhexPfwHlIra5/EJCWklvvpbA=; fh=GLr2v/Gy8kpMTOFeMG/hG66rnRJjT29uNVk4Vbz+hWg=; b=LGM6O+VMVM6X6UPs9zsZAUaNi7RTLv1zASJKZSRFFYECicrcxlK8ZJL8aSSIUV43pF CWuRyJLuaBChMVY2BUcV3tga6vpYTXBZ2H7DWMzwEfNYWi2sIaF2E4Dvw2N5frwqHP9C LltjuLk0I9IegmnxMgLagtW1+QH3hQ2VSUpdoY14Y7m265rwqNUMwBkmbcfMAjATl+ly LTRYw902WHpJAVVkXKNUF4eJHv4jRj+QKi6NYHqd8iNw6Zi9cg17oib4EzeohL4aWWro trJ+U+uCFmmCh31EmVnpV9SHxtWrmGMwvvCmtq/ZfDBLs+dnI3jRjPezfxS/aY4PWlSU vCOw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=R0mZTZ0R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l8-20020aa7cac8000000b0051be7209485si5586637edt.457.2023.06.28.11.49.56; Wed, 28 Jun 2023 11:50:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=R0mZTZ0R; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S230413AbjF1Sdn (ORCPT + 99 others); Wed, 28 Jun 2023 14:33:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49894 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232059AbjF1Sdj (ORCPT ); Wed, 28 Jun 2023 14:33:39 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DB8A91FE4; Wed, 28 Jun 2023 11:33:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 7113761418; Wed, 28 Jun 2023 18:33:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A9501C433C8; Wed, 28 Jun 2023 18:33:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687977216; bh=PQylG1KdUstc1Cg/WoQUG20kCsvwqf/NgHAmIMpuUdk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=R0mZTZ0RKj5JbYPa2WjnbY8Bh47st/gO0VHS3b5WH+rsBw0D7pOpXT/oaLkQxh23H skGrGU1yvdjS5oiBwPxLxDGaGjOBYaKJBw/hlwdow+V1/+EbAcEo5JMKjqoWOnSDhI 3TBG5UJR7iDP1syCoubUPXOi02b1Dk8gICHcCtLWlLIIOVh4AhZCd3faTF46mUnwZh HO2eQxW5w4e7bx6XbfpNPa1Q6xUamE0ejIVEDKDjfGdgpSxWw37AAJsh3cRCK3tHh7 l2LmUTH2juuaBKuRRPjxCCweNdps5BLbgGLPs9FsCkHx0JTIihms5JYcrTfrkCmocn r1DFGh2eMLZRQ== Date: Wed, 28 Jun 2023 11:33:35 -0700 From: Jaegeuk Kim To: Chao Yu Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, stable@vger.kernel.org Subject: Re: [PATCH v2] f2fs: fix deadlock in i_xattr_sem and inode page lock and fix the original issue Message-ID: References: <20230613233940.3643362-1-jaegeuk@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/28, Chao Yu wrote: > On 2023/6/28 16:08, Jaegeuk Kim wrote: > > Thread #1: > > > > [122554.641906][ T92] f2fs_getxattr+0xd4/0x5fc > > -> waiting for f2fs_down_read(&F2FS_I(inode)->i_xattr_sem); > > > > [122554.641927][ T92] __f2fs_get_acl+0x50/0x284 > > [122554.641948][ T92] f2fs_init_acl+0x84/0x54c > > [122554.641969][ T92] f2fs_init_inode_metadata+0x460/0x5f0 > > [122554.641990][ T92] f2fs_add_inline_entry+0x11c/0x350 > > -> Locked dir->inode_page by f2fs_get_node_page() > > > > [122554.642009][ T92] f2fs_do_add_link+0x100/0x1e4 > > [122554.642025][ T92] f2fs_create+0xf4/0x22c > > [122554.642047][ T92] vfs_create+0x130/0x1f4 > > > > Thread #2: > > > > [123996.386358][ T92] __get_node_page+0x8c/0x504 > > -> waiting for dir->inode_page lock > > > > [123996.386383][ T92] read_all_xattrs+0x11c/0x1f4 > > [123996.386405][ T92] __f2fs_setxattr+0xcc/0x528 > > [123996.386424][ T92] f2fs_setxattr+0x158/0x1f4 > > -> f2fs_down_write(&F2FS_I(inode)->i_xattr_sem); > > > > [123996.386443][ T92] __f2fs_set_acl+0x328/0x430 > > [123996.386618][ T92] f2fs_set_acl+0x38/0x50 > > [123996.386642][ T92] posix_acl_chmod+0xc8/0x1c8 > > [123996.386669][ T92] f2fs_setattr+0x5e0/0x6bc > > [123996.386689][ T92] notify_change+0x4d8/0x580 > > [123996.386717][ T92] chmod_common+0xd8/0x184 > > [123996.386748][ T92] do_fchmodat+0x60/0x124 > > [123996.386766][ T92] __arm64_sys_fchmodat+0x28/0x3c > > Back to the race condition, my question is why we can chmod on inode before > it has been created? This is touching the directory. > > Thanks, > > > > > Fixes: 27161f13e3c3 "f2fs: avoid race in between read xattr & write xattr" > > Cc: > > Signed-off-by: Jaegeuk Kim > > --- > > fs/f2fs/dir.c | 9 ++++++++- > > fs/f2fs/xattr.c | 6 ++++-- > > 2 files changed, 12 insertions(+), 3 deletions(-) > > > > diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c > > index 887e55988450..d635c58cf5a3 100644 > > --- a/fs/f2fs/dir.c > > +++ b/fs/f2fs/dir.c > > @@ -775,8 +775,15 @@ int f2fs_add_dentry(struct inode *dir, const struct f2fs_filename *fname, > > { > > int err = -EAGAIN; > > - if (f2fs_has_inline_dentry(dir)) > > + if (f2fs_has_inline_dentry(dir)) { > > + /* > > + * Should get i_xattr_sem to keep the lock order: > > + * i_xattr_sem -> inode_page lock used by f2fs_setxattr. > > + */ > > + f2fs_down_read(&F2FS_I(dir)->i_xattr_sem); > > err = f2fs_add_inline_entry(dir, fname, inode, ino, mode); > > + f2fs_up_read(&F2FS_I(dir)->i_xattr_sem); > > + } > > if (err == -EAGAIN) > > err = f2fs_add_regular_entry(dir, fname, inode, ino, mode); > > diff --git a/fs/f2fs/xattr.c b/fs/f2fs/xattr.c > > index 213805d3592c..476b186b90a6 100644 > > --- a/fs/f2fs/xattr.c > > +++ b/fs/f2fs/xattr.c > > @@ -528,10 +528,12 @@ int f2fs_getxattr(struct inode *inode, int index, const char *name, > > if (len > F2FS_NAME_LEN) > > return -ERANGE; > > - f2fs_down_read(&F2FS_I(inode)->i_xattr_sem); > > + if (!ipage) > > + f2fs_down_read(&F2FS_I(inode)->i_xattr_sem); > > error = lookup_all_xattrs(inode, ipage, index, len, name, > > &entry, &base_addr, &base_size, &is_inline); > > - f2fs_up_read(&F2FS_I(inode)->i_xattr_sem); > > + if (!ipage) > > + f2fs_up_read(&F2FS_I(inode)->i_xattr_sem); > > if (error) > > return error;