Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp168453yba; Fri, 5 Apr 2019 04:25:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqwoW5qp1cYJIF8nXbYq+uEnX+Cz6crsFtdtM5kbyYnSwyZi0fyQi1ApRyKZSxqktvcaPc+w X-Received: by 2002:a62:b612:: with SMTP id j18mr12095690pff.124.1554463512771; Fri, 05 Apr 2019 04:25:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554463512; cv=none; d=google.com; s=arc-20160816; b=gT/SA2eFDPPn1yG0zb3/0HSwtOeCCAXSEvvwWkVZH8YeSPdWSCUBV18QLOAgAUqkPZ 5DXiIfsGSEUru1cAUWJRlmOYKrgvr1il9wbfgDbD5m6J5/tP57n1Ffscjqgzc/0oPEeT UCejxGJ8oYn0HgtAHJPtQ5qN3O/rS8wt6ItTeiPjG/HtEJkQdRNS5e3YU0GDycUpuxaE 2lWy2VClzp1p7vTvGWHnPmfOSHpMMnj22vWZipxBzgibDV3oh/JrD0rjx/NqtTJify51 6VZFoyDAqOIS+S72XOZli3XrEnyB26e+v8JSeHfUtgTe4AP6EwFo5xGB7+ZPu2ASvrAt NhzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=53zdec592suQ9g1BpKnSPJGBubxqFKYqc277P1wcos8=; b=WjlKkKJ7hazz8TFgLowVdw3qi8jl2wkJIhPf+0snv6dKT4V19l1X1h7rOjTqZOl+4N PtC1waTbtFFCdn62iD1bG41BO9/7ZY7DyjZZ1NfZb/STWk7E/b3V9z5d7IkMDgj+4nkN AT92L2XoxG9RoEv1MTA/QP878S2E0tYn4DRrI9wMU60EwBRvzT1JHK0MomD3/F9EPrWC vjKK4AYfU0mx7n7w6UTAhNgnj4NySKah1vsu9frVdv1tOUcnSKr8aA4bqLCCSvUw6+G8 d+G5QMHBliiEGowLOU+78H6rvMHdRN8McsnkLDGE3N6MfQMJFbzMvMh0mnZ2KvQZxKta HTvQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bd9si18401931plb.208.2019.04.05.04.24.57; Fri, 05 Apr 2019 04:25:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730853AbfDELW6 (ORCPT + 99 others); Fri, 5 Apr 2019 07:22:58 -0400 Received: from alexa-out-blr-02.qualcomm.com ([103.229.18.198]:7010 "EHLO alexa-out-blr.qualcomm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730642AbfDELW6 (ORCPT ); Fri, 5 Apr 2019 07:22:58 -0400 X-IronPort-AV: E=Sophos;i="5.60,312,1549909800"; d="scan'208";a="405517" Received: from ironmsg01-blr.qualcomm.com ([10.86.208.130]) by alexa-out-blr.qualcomm.com with ESMTP/TLS/AES256-SHA; 05 Apr 2019 16:51:10 +0530 X-IronPort-AV: E=McAfee;i="5900,7806,9217"; a="8432704" Received: from gkohli-linux.qualcomm.com ([10.204.78.26]) by ironmsg01-blr.qualcomm.com with ESMTP; 05 Apr 2019 16:51:10 +0530 Received: by gkohli-linux.qualcomm.com (Postfix, from userid 427023) id EC9AE3BB0; Fri, 5 Apr 2019 16:51:08 +0530 (IST) From: Gaurav Kohli To: gregkh@linuxfoundation.org, tj@kernel.org, linux-kernel@vger.kernel.org Cc: linux-arm-msm@vger.kernel.org, Gaurav Kohli , Mukesh Ojha Subject: [PATCH v0] kernfs: Skip kernfs_put of parent from child node Date: Fri, 5 Apr 2019 16:51:07 +0530 Message-Id: <1554463267-30841-1-git-send-email-gkohli@codeaurora.org> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While adding kernfs node for child to the parent kernfs node and when child node founds that parent kn count is zero, then below comes like: WARNING: fs/kernfs/dir.c:494 kernfs_get+0x64/0x88 This indicates that parent is in kernfs_put path/ or already freed, and if the child node keeps continue to make new kernfs node, then there is chance of below race for parent node: CPU0 CPU1 //Parent node //child node kernfs_put atomic_dec_and_test(&kn->count) //count is 0, so continue kernfs_new_node(child) kernfs_get(parent); //increment parent count to 1 //warning come as parent count is 0 /* link in */ kernfs_add_one(kn); // this should fail as parent is //in free path. kernfs_put(child) kmem_cache_free(parent) kmem_cache_free(child) kn = parent atomic_dec_and_test(&kn->count)) //this is 0 now, so release will continue for parent. kmem_cache_free(parent) To prevent this race, child simply has to decrement count of parent kernfs node and keep continue the free path for itself. Signed-off-by: Gaurav Kohli Signed-off-by: Mukesh Ojha diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c index b84d635..d5a36e8 100644 --- a/fs/kernfs/dir.c +++ b/fs/kernfs/dir.c @@ -515,7 +515,6 @@ void kernfs_put(struct kernfs_node *kn) if (!kn || !atomic_dec_and_test(&kn->count)) return; root = kernfs_root(kn); - repeat: /* * Moving/renaming is always done while holding reference. * kn->parent won't change beneath us. @@ -545,8 +544,8 @@ void kernfs_put(struct kernfs_node *kn) kn = parent; if (kn) { - if (atomic_dec_and_test(&kn->count)) - goto repeat; + /* Parent may be on free path, so simply decrement the count */ + atomic_dec_and_test(&kn->count); } else { /* just released the root kn, free @root too */ idr_destroy(&root->ino_idr); -- Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project