Message ID | 20230527014018.47396-3-yebin10@huawei.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp75698vqr; Fri, 26 May 2023 18:58:51 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6Aro1kLY2P0s0TFO9DII9rkYlbMk089gTBaUnaFZOb6/t4MDJdDfKbgJr1GpKgkHx0kbs/ X-Received: by 2002:a05:6a00:2e02:b0:64d:68dc:b942 with SMTP id fc2-20020a056a002e0200b0064d68dcb942mr7645191pfb.7.1685152731077; Fri, 26 May 2023 18:58:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685152731; cv=none; d=google.com; s=arc-20160816; b=DzxsWpLLebz71WRGpLkFJmsvf+KCsZlnbj0kahd7aJQTq28ZrFtd4bWtLiVkUJrFuB 0Gtgg2Iyjst5iNSgAV4d09ZI/wEN6Bj8w4lYLtscSdroJXyd9EgprDuJi9zxLS9zR2iz 3yZVII9J6rHuyH8qww8QVIzAi5vyU3Sj1VtWDsufbVXtAHw7KDHLXXzYgaC55ijyF9S2 lmXPuwRXW83w9A0Qmn608iBkjkjOoNsWA2iXEKiiwX2jN+RyqtWxuONjVmMB4Z5Y9u5o aPEe/xoyQkcIi/ooF8FXPoZa2+lmGImmGkliN0ND/B6xVBVl0a8o/XVZwVeVVCLfviRj LjCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=zV3yEQ/sIlNz0A+Gg187/Q5GR6zz7TuyVYbBzxkAZhk=; b=l7Fv5ncBfY8P9nLr86jbKopvXfS5ZjhZ/ZGcuNcwcdHpbZ3M0MTmospxde9YI5M3bu 3nllCXDKeDrwCmD6YBs9SYoPtdOmyZxVOwhCaHZinsgO4ObgqUVBGrspXnI9Ewg956Ez 0NglGxp+xFnMwkR9vGQfYd+B/+AfKz4BrRaMkwDZUo6e2xFenZs7y70rnJ/vhpEKRAMe IQpookizIXucQoVISZcN//ilhYLXJzQHrQT+ZsBfcA/nzt6oQJwB06kmpdZszYFBTbvO jlnRLB8nTBsCJ6X+3l7oOplvMucWjcdzxGBrjIAFzbM2mCIn2gf9kjgmJSMSPD/gzZB2 vWZQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k24-20020aa79738000000b00643c4d0d0f5si3124353pfg.39.2023.05.26.18.58.37; Fri, 26 May 2023 18:58:51 -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; 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=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241965AbjE0BmF (ORCPT <rfc822;zhanglyra.2023@gmail.com> + 99 others); Fri, 26 May 2023 21:42:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35164 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230179AbjE0BmB (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 26 May 2023 21:42:01 -0400 Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CBA7AFB for <linux-kernel@vger.kernel.org>; Fri, 26 May 2023 18:41:59 -0700 (PDT) Received: from canpemm500010.china.huawei.com (unknown [172.30.72.56]) by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4QSky26JXzzLmPR; Sat, 27 May 2023 09:40:26 +0800 (CST) Received: from huawei.com (10.175.127.227) by canpemm500010.china.huawei.com (7.192.105.118) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Sat, 27 May 2023 09:41:57 +0800 From: Ye Bin <yebin10@huawei.com> To: <jack@suse.com>, <linux-kernel@vger.kernel.org> CC: <yebin10@huawei.com> Subject: [PATCH 2/2] quota: fix warning in dqgrab() Date: Sat, 27 May 2023 09:40:18 +0800 Message-ID: <20230527014018.47396-3-yebin10@huawei.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20230527014018.47396-1-yebin10@huawei.com> References: <20230527014018.47396-1-yebin10@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=US-ASCII X-Originating-IP: [10.175.127.227] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To canpemm500010.china.huawei.com (7.192.105.118) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1767010710107137643?= X-GMAIL-MSGID: =?utf-8?q?1767010710107137643?= |
Series |
fix two issue about quota
|
|
Commit Message
Ye Bin
May 27, 2023, 1:40 a.m. UTC
There's issue as follows when do fault injection:
WARNING: CPU: 1 PID: 14870 at include/linux/quotaops.h:51 dquot_disable+0x13b7/0x18c0
Modules linked in:
CPU: 1 PID: 14870 Comm: fsconfig Not tainted 6.3.0-next-20230505-00006-g5107a9c821af-dirty #541
RIP: 0010:dquot_disable+0x13b7/0x18c0
RSP: 0018:ffffc9000acc79e0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88825e41b980
RDX: 0000000000000000 RSI: ffff88825e41b980 RDI: 0000000000000002
RBP: ffff888179f68000 R08: ffffffff82087ca7 R09: 0000000000000000
R10: 0000000000000001 R11: ffffed102f3ed026 R12: ffff888179f68130
R13: ffff888179f68110 R14: dffffc0000000000 R15: ffff888179f68118
FS: 00007f450a073740(0000) GS:ffff88882fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe96f2efd8 CR3: 000000025c8ad000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dquot_load_quota_sb+0xd53/0x1060
dquot_resume+0x172/0x230
ext4_reconfigure+0x1dc6/0x27b0
reconfigure_super+0x515/0xa90
__x64_sys_fsconfig+0xb19/0xd20
do_syscall_64+0x39/0xb0
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Above issue may happens as follows:
ProcessA ProcessB ProcessC
sys_fsconfig
vfs_fsconfig_locked
reconfigure_super
ext4_remount
dquot_suspend -> suspend all type quota
sys_fsconfig
vfs_fsconfig_locked
reconfigure_super
ext4_remount
dquot_resume
ret = dquot_load_quota_sb
add_dquot_ref
do_open -> open file O_RDWR
vfs_open
do_dentry_open
get_write_access
atomic_inc_unless_negative(&inode->i_writecount)
ext4_file_open
dquot_file_open
dquot_initialize
__dquot_initialize
dqget
atomic_inc(&dquot->dq_count);
__dquot_initialize
__dquot_initialize
dqget
if (!test_bit(DQ_ACTIVE_B, &dquot->dq_flags))
ext4_acquire_dquot
-> Return error DQ_ACTIVE_B flag isn't set
dquot_disable
invalidate_dquots
if (atomic_read(&dquot->dq_count))
dqgrab
WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags))
-> Trigger warning
In the above scenario, 'dquot->dq_flags' has no DQ_ACTIVE_B is normal when
dqgrab().
So just remove 'WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags))'
in dqgrab().
Signed-off-by: Ye Bin <yebin10@huawei.com>
---
include/linux/quotaops.h | 1 -
1 file changed, 1 deletion(-)
Comments
On Sat 27-05-23 09:40:18, Ye Bin wrote: > There's issue as follows when do fault injection: > WARNING: CPU: 1 PID: 14870 at include/linux/quotaops.h:51 dquot_disable+0x13b7/0x18c0 > Modules linked in: > CPU: 1 PID: 14870 Comm: fsconfig Not tainted 6.3.0-next-20230505-00006-g5107a9c821af-dirty #541 > RIP: 0010:dquot_disable+0x13b7/0x18c0 > RSP: 0018:ffffc9000acc79e0 EFLAGS: 00010246 > RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88825e41b980 > RDX: 0000000000000000 RSI: ffff88825e41b980 RDI: 0000000000000002 > RBP: ffff888179f68000 R08: ffffffff82087ca7 R09: 0000000000000000 > R10: 0000000000000001 R11: ffffed102f3ed026 R12: ffff888179f68130 > R13: ffff888179f68110 R14: dffffc0000000000 R15: ffff888179f68118 > FS: 00007f450a073740(0000) GS:ffff88882fc00000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007ffe96f2efd8 CR3: 000000025c8ad000 CR4: 00000000000006e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > <TASK> > dquot_load_quota_sb+0xd53/0x1060 > dquot_resume+0x172/0x230 > ext4_reconfigure+0x1dc6/0x27b0 > reconfigure_super+0x515/0xa90 > __x64_sys_fsconfig+0xb19/0xd20 > do_syscall_64+0x39/0xb0 > entry_SYSCALL_64_after_hwframe+0x63/0xcd > > Above issue may happens as follows: > ProcessA ProcessB ProcessC > sys_fsconfig > vfs_fsconfig_locked > reconfigure_super > ext4_remount > dquot_suspend -> suspend all type quota > > sys_fsconfig > vfs_fsconfig_locked > reconfigure_super > ext4_remount > dquot_resume > ret = dquot_load_quota_sb > add_dquot_ref > do_open -> open file O_RDWR > vfs_open > do_dentry_open > get_write_access > atomic_inc_unless_negative(&inode->i_writecount) > ext4_file_open > dquot_file_open > dquot_initialize > __dquot_initialize > dqget > atomic_inc(&dquot->dq_count); > > __dquot_initialize > __dquot_initialize > dqget > if (!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)) > ext4_acquire_dquot > -> Return error DQ_ACTIVE_B flag isn't set > dquot_disable > invalidate_dquots > if (atomic_read(&dquot->dq_count)) > dqgrab > WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)) > -> Trigger warning > > In the above scenario, 'dquot->dq_flags' has no DQ_ACTIVE_B is normal when > dqgrab(). > So just remove 'WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags))' > in dqgrab(). > > Signed-off-by: Ye Bin <yebin10@huawei.com> Thanks for the patch! Actually rather than deleting the assertion from dqgrab() (which can be and is used by filesystems) I'd replace the dqgrab() use in invalidate_dquots() with plain: atomic_inc(&dquot->dq_count); Honza > --- > include/linux/quotaops.h | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/include/linux/quotaops.h b/include/linux/quotaops.h > index 11a4becff3a9..cb5e4c11e503 100644 > --- a/include/linux/quotaops.h > +++ b/include/linux/quotaops.h > @@ -48,7 +48,6 @@ static inline struct dquot *dqgrab(struct dquot *dquot) > { > /* Make sure someone else has active reference to dquot */ > WARN_ON_ONCE(!atomic_read(&dquot->dq_count)); > - WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)); > atomic_inc(&dquot->dq_count); > return dquot; > } > -- > 2.31.1 >
On 2023/5/30 18:15, Jan Kara wrote: > On Sat 27-05-23 09:40:18, Ye Bin wrote: >> There's issue as follows when do fault injection: >> WARNING: CPU: 1 PID: 14870 at include/linux/quotaops.h:51 dquot_disable+0x13b7/0x18c0 >> Modules linked in: >> CPU: 1 PID: 14870 Comm: fsconfig Not tainted 6.3.0-next-20230505-00006-g5107a9c821af-dirty #541 >> RIP: 0010:dquot_disable+0x13b7/0x18c0 >> RSP: 0018:ffffc9000acc79e0 EFLAGS: 00010246 >> RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88825e41b980 >> RDX: 0000000000000000 RSI: ffff88825e41b980 RDI: 0000000000000002 >> RBP: ffff888179f68000 R08: ffffffff82087ca7 R09: 0000000000000000 >> R10: 0000000000000001 R11: ffffed102f3ed026 R12: ffff888179f68130 >> R13: ffff888179f68110 R14: dffffc0000000000 R15: ffff888179f68118 >> FS: 00007f450a073740(0000) GS:ffff88882fc00000(0000) knlGS:0000000000000000 >> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >> CR2: 00007ffe96f2efd8 CR3: 000000025c8ad000 CR4: 00000000000006e0 >> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 >> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 >> Call Trace: >> <TASK> >> dquot_load_quota_sb+0xd53/0x1060 >> dquot_resume+0x172/0x230 >> ext4_reconfigure+0x1dc6/0x27b0 >> reconfigure_super+0x515/0xa90 >> __x64_sys_fsconfig+0xb19/0xd20 >> do_syscall_64+0x39/0xb0 >> entry_SYSCALL_64_after_hwframe+0x63/0xcd >> >> Above issue may happens as follows: >> ProcessA ProcessB ProcessC >> sys_fsconfig >> vfs_fsconfig_locked >> reconfigure_super >> ext4_remount >> dquot_suspend -> suspend all type quota >> >> sys_fsconfig >> vfs_fsconfig_locked >> reconfigure_super >> ext4_remount >> dquot_resume >> ret = dquot_load_quota_sb >> add_dquot_ref >> do_open -> open file O_RDWR >> vfs_open >> do_dentry_open >> get_write_access >> atomic_inc_unless_negative(&inode->i_writecount) >> ext4_file_open >> dquot_file_open >> dquot_initialize >> __dquot_initialize >> dqget >> atomic_inc(&dquot->dq_count); >> >> __dquot_initialize >> __dquot_initialize >> dqget >> if (!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)) >> ext4_acquire_dquot >> -> Return error DQ_ACTIVE_B flag isn't set >> dquot_disable >> invalidate_dquots >> if (atomic_read(&dquot->dq_count)) >> dqgrab >> WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)) >> -> Trigger warning >> >> In the above scenario, 'dquot->dq_flags' has no DQ_ACTIVE_B is normal when >> dqgrab(). >> So just remove 'WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags))' >> in dqgrab(). >> >> Signed-off-by: Ye Bin <yebin10@huawei.com> > Thanks for the patch! Actually rather than deleting the assertion from > dqgrab() (which can be and is used by filesystems) I'd replace the dqgrab() > use in invalidate_dquots() with plain: > > atomic_inc(&dquot->dq_count); > > Honza This is indeed a good idea, I will send a new version. >> --- >> include/linux/quotaops.h | 1 - >> 1 file changed, 1 deletion(-) >> >> diff --git a/include/linux/quotaops.h b/include/linux/quotaops.h >> index 11a4becff3a9..cb5e4c11e503 100644 >> --- a/include/linux/quotaops.h >> +++ b/include/linux/quotaops.h >> @@ -48,7 +48,6 @@ static inline struct dquot *dqgrab(struct dquot *dquot) >> { >> /* Make sure someone else has active reference to dquot */ >> WARN_ON_ONCE(!atomic_read(&dquot->dq_count)); >> - WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)); >> atomic_inc(&dquot->dq_count); >> return dquot; >> } >> -- >> 2.31.1 >>
diff --git a/include/linux/quotaops.h b/include/linux/quotaops.h index 11a4becff3a9..cb5e4c11e503 100644 --- a/include/linux/quotaops.h +++ b/include/linux/quotaops.h @@ -48,7 +48,6 @@ static inline struct dquot *dqgrab(struct dquot *dquot) { /* Make sure someone else has active reference to dquot */ WARN_ON_ONCE(!atomic_read(&dquot->dq_count)); - WARN_ON_ONCE(!test_bit(DQ_ACTIVE_B, &dquot->dq_flags)); atomic_inc(&dquot->dq_count); return dquot; }