Received: by 10.192.165.156 with SMTP id m28csp1522097imm; Tue, 17 Apr 2018 00:15:01 -0700 (PDT) X-Google-Smtp-Source: AIpwx49ALRygTeolIBja3h26NS8c+4jwQzk9XAS4XqL9mgY4RCohiDiE7SaWtIVRP3CeHmRmntA1 X-Received: by 10.98.137.16 with SMTP id v16mr747938pfd.13.1523949301750; Tue, 17 Apr 2018 00:15:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523949301; cv=none; d=google.com; s=arc-20160816; b=cuK36MEeJ1+rjE0sm7N9pCOtlIPqEWyx1LVNvVCxe+DaFGereQQhVKpAC4/JLtehie 8N/lrmiwiolt1i4pr60+Vau7N+hPyZDNdeTWUi5lwJ+jDIce/n0N6g/J2A7E93KpFi0e uLRvYkG0hBIRBSsTKhwLVoo56Kdpdmr4zxNcRkMh+Rk240JMapLWYRI80e70kD3v2li7 UZQWNLG56/gXXDuANRj/LFf2Ieq0uMzdckIA3DCWcCoCNC2p6eR/lv0WOtxfJaCOOiX6 +gKdyZQZwQlzAkFq72vqUh4MgtMpSylGLJExg/8VWgKS2T8mz/1DSANHDiEL9ZXyJ9cD e5zA== 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 :arc-authentication-results; bh=GTvLD87BMZZDrVjpmiux/Ek0Q3Xpz0Z7Q1EWDpbNgAs=; b=KZKK0kNsxjYfFWNnvK21UdvQ9+BXpfIGlvX8bMUsZQzPMevjod+1dsQCrJvuVWaQJy D3iasy1Fv+MX0Uskl84cV9JLCXreuzj0i65LPacE3OpWUT74NCGhd6bjcZgqjLGQ4feQ J8e6icfWRVUhpg56H/W+f/5MfuQt/yaMPcOJpDFyTc0s++pN93Wx7IIGHPGapFJTw22O MO04A3bN4eI5aBx0BtR6BUI+V9eArHVphXf/BlU5YoNo2ig63npp2tCahMA2uVTxKSRP GieArrlZTLLsQvFxi9edeJvNous7Wg2ug8SAie9YZVjJcfXTQYVCn6ZynDob1hnvGKl0 vGSA== 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 b3-v6si13471106pla.505.2018.04.17.00.14.48; Tue, 17 Apr 2018 00:15:01 -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 S1751878AbeDQHNk (ORCPT + 99 others); Tue, 17 Apr 2018 03:13:40 -0400 Received: from out1.zte.com.cn ([202.103.147.172]:60392 "EHLO mxct.zte.com.cn" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750971AbeDQHNi (ORCPT ); Tue, 17 Apr 2018 03:13:38 -0400 Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Forcepoint Email with ESMTPS id DCEF8EB582BD34B2F97E; Tue, 17 Apr 2018 15:13:33 +0800 (CST) Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id w3H7DF72068129; Tue, 17 Apr 2018 15:13:15 +0800 (GMT-8) (envelope-from jiang.biao2@zte.com.cn) Received: from localhost.localdomain ([10.75.10.200]) by szsmtp06.zte.com.cn (Lotus Domino Release 8.5.3FP6) with ESMTP id 2018041715131933-5774911 ; Tue, 17 Apr 2018 15:13:19 +0800 From: Jiang Biao To: axboe@kernel.dk Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, tj@kernel.org, jiang.biao2@zte.com.cn, zhong.weidong@zte.com.cn, wen.yang99@zte.com.cn Subject: [PATCH] blkcg: not hold blkcg lock when deactivating policy. Date: Tue, 17 Apr 2018 15:10:33 +0800 Message-Id: <1523949033-91148-1-git-send-email-jiang.biao2@zte.com.cn> X-Mailer: git-send-email 1.8.3.1 X-MIMETrack: Itemize by SMTP Server on SZSMTP06/server/zte_ltd(Release 8.5.3FP6|November 21, 2013) at 2018-04-17 15:13:19, Serialize by Router on notes_smtp/zte_ltd(Release 9.0.1FP7|August 17, 2016) at 2018-04-17 15:13:11, Serialize complete at 2018-04-17 15:13:11 X-MAIL: mse01.zte.com.cn w3H7DF72068129 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As described in the comment of blkcg_activate_policy(), *Update of each blkg is protected by both queue and blkcg locks so that holding either lock and testing blkcg_policy_enabled() is always enough for dereferencing policy data.* with queue lock held, there is no need to hold blkcg lock in blkcg_deactivate_policy(). Similar case is in blkcg_activate_policy(), which has removed holding of blkcg lock in commit 4c55f4f9ad3001ac1fefdd8d8ca7641d18558e23. Signed-off-by: Jiang Biao Signed-off-by: Wen Yang CC: Tejun Heo CC: Jens Axboe --- block/blk-cgroup.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c index c2033a2..2b7f8d0 100644 --- a/block/blk-cgroup.c +++ b/block/blk-cgroup.c @@ -1367,17 +1367,12 @@ void blkcg_deactivate_policy(struct request_queue *q, __clear_bit(pol->plid, q->blkcg_pols); list_for_each_entry(blkg, &q->blkg_list, q_node) { - /* grab blkcg lock too while removing @pd from @blkg */ - spin_lock(&blkg->blkcg->lock); - if (blkg->pd[pol->plid]) { if (pol->pd_offline_fn) pol->pd_offline_fn(blkg->pd[pol->plid]); pol->pd_free_fn(blkg->pd[pol->plid]); blkg->pd[pol->plid] = NULL; } - - spin_unlock(&blkg->blkcg->lock); } spin_unlock_irq(q->queue_lock); -- 2.7.4