Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752245AbdC0SiZ (ORCPT ); Mon, 27 Mar 2017 14:38:25 -0400 Received: from mail-it0-f41.google.com ([209.85.214.41]:37413 "EHLO mail-it0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752197AbdC0SiX (ORCPT ); Mon, 27 Mar 2017 14:38:23 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Tahsin Erdogan Date: Mon, 27 Mar 2017 11:29:18 -0700 Message-ID: Subject: Re: [PATCH] blkcg: allocate struct blkcg_gq outside request queue spinlock To: Julia Lawall Cc: Tejun Heo , Jens Axboe , linux-block@vger.kernel.org, David Rientjes , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 375 Lines: 9 On Sun, Mar 26, 2017 at 3:54 AM, Julia Lawall wrote: > Is an unlock needed before line 848? Or does blkg_lookup_check take care > of it? Unlock is not needed. On success, function returns with locks held. It is documented at line 805: "... This function returns with RCU read * lock and queue lock held and must be paired with blkg_conf_finish()."