Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp183857rwl; Wed, 4 Jan 2023 17:26:50 -0800 (PST) X-Google-Smtp-Source: AMrXdXtjjUqReK1FQXbXH8iFMcKj0JjrvCndexPDXEuRE/CzJRpBn+WGfFr9X5z6K6q14p8oqTMn X-Received: by 2002:a17:906:6d2:b0:7e7:4dd7:bb88 with SMTP id v18-20020a17090606d200b007e74dd7bb88mr39361731ejb.57.1672882009875; Wed, 04 Jan 2023 17:26:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672882009; cv=none; d=google.com; s=arc-20160816; b=XbHgQmKNDmOzhw516BfAVBCQCZQ/aj6c2s5swamKk3ZMlez8QPAjOsHUK+77BkdMz8 H8NE40sCWNTPWTAnATEiEoTrkHm6fj+kqyCfIWD8JMNTaEDKsa5Vo47KdM/UULlfn7mr BW0EF/0ujVeaVebWXhvyee6xf8mlLqYyLzlw5w4mkETKodvwL62EO24i0UVGoEWlnKDx ioLqvJFikU2epURTcVSgXFJtnORZBynxvev1GXMjnJAUnmPhk+gBZTsAETgLJKxZVZUP d+YoJaPtBV+HFgDxGS6CdUX9mPnAy37VPB2XZJ01vJC4CJl0NynP6a9NT215XycVUTlY cCKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=mDDp5BMkNO/89ccjytmTcd1XWVtWXCtZAFcG+ibq7Is=; b=EaN7q90tOEFG1WU0LGiSlwcUJBx07AbiLFG5RZbRQGOoZ/xSJFpYqq1ZN+cVfOAwX+ CYHjQPRDQtN9f7/FCSd9FWoFqIAKHjf6ewlUgD3PDlzR9GaVOhJtigKgruPn1n2Ho9N6 2fU8F/DIwNqtIG4S/YaRGr19sZUBvlAG09KlfMrGgdloEpv42lGYI7KG4Vw8/EH34A6d kG0n1sDxwsUBGsuPyf7uOymFulVrBk8RDEDx+DLyADU9STrSr+KfYy8w1gNlLQ/zoS09 fF2ozXJTkzS9tb0v9oe1UJeXsOWYONRKQhYi2dnIos92Q6u8MPIMduQz7dMiXLnXNKvH kzlA== 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e4-20020a17090658c400b0084c7b099652si21934538ejs.567.2023.01.04.17.26.36; Wed, 04 Jan 2023 17:26:49 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230161AbjAEBO6 (ORCPT + 56 others); Wed, 4 Jan 2023 20:14:58 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51380 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230181AbjAEBO2 (ORCPT ); Wed, 4 Jan 2023 20:14:28 -0500 Received: from dggsgout11.his.huawei.com (unknown [45.249.212.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8847B44353; Wed, 4 Jan 2023 17:14:12 -0800 (PST) Received: from mail02.huawei.com (unknown [172.30.67.153]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTP id 4NnT5B6cFzz4f3vf5; Thu, 5 Jan 2023 09:14:06 +0800 (CST) Received: from [10.174.176.73] (unknown [10.174.176.73]) by APP4 (Coremail) with SMTP id gCh0CgD3rLBfJLZjS1R6BA--.60579S3; Thu, 05 Jan 2023 09:14:09 +0800 (CST) Subject: Re: [PATCH v2 1/2] blk-iocost: add refcounting for iocg To: Tejun Heo , Yu Kuai Cc: hch@infradead.org, josef@toxicpanda.com, axboe@kernel.dk, cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, yi.zhang@huawei.com, "yukuai (C)" References: <20221227125502.541931-1-yukuai1@huaweicloud.com> <20221227125502.541931-2-yukuai1@huaweicloud.com> From: Yu Kuai Message-ID: Date: Thu, 5 Jan 2023 09:14:07 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=gbk; format=flowed Content-Transfer-Encoding: 8bit X-CM-TRANSID: gCh0CgD3rLBfJLZjS1R6BA--.60579S3 X-Coremail-Antispam: 1UD129KBjvJXoW7uFy3tryxWryxJry8tF18Krg_yoW8GrWDpa 97Gas0k398Xr1IkFsFya1jq34rKw4rXrWrGrWkGryrA3yxCwnF9rWjyrW5Ca4rZF4fXF1Y qF1Sva1UGw4jya7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU9Y14x267AKxVW8JVW5JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0 rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2AK02 1l84ACjcxK6xIIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY6xkF7I0E14v26r4U JVWxJr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Gc CE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E 2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJV W8JwACjcxG0xvEwIxGrwACjI8F5VA0II8E6IAqYI8I648v4I1lFIxGxcIEc7CjxVA2Y2ka 0xkIwI1lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7x kEbVWUJVW8JwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E 67AF67kF1VAFwI0_Jw0_GFylIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCw CI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E 3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCT nIWIevJa73UjIFyTuYvjfUoOJ5UUUUU X-CM-SenderInfo: 51xn3trlr6x35dzhxuhorxvhhfrp/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS 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 Hi, ?? 2023/01/05 5:44, Tejun Heo ะด??: > On Tue, Dec 27, 2022 at 08:55:01PM +0800, Yu Kuai wrote: >> From: Yu Kuai >> >> iocost requires that child iocg must exit before parent iocg, otherwise >> kernel might crash in ioc_timer_fn(). However, currently iocg is exited >> in pd_free_fn(), which can't guarantee such order: >> >> 1) remove cgroup can concurrent with deactivate policy; >> 2) blkg_free() triggered by remove cgroup is asynchronously, remove >> child cgroup can concurrent with remove parent cgroup; >> >> Fix the problem by add refcounting for iocg, and child iocg will grab >> reference of parent iocg, so that parent iocg will wait for all child >> iocg to be exited. > > Wouldn't it be better to do this refcnting in the blk-cgroup core code > rather than in blk-iocost? > The problem is that I can't find a proper way to fix the competition that pd_free_fn() can be called from different context: 1) from blkg_free() that is called asynchronously from removing cgroup; 2) from blkcg_deactivate_policy() that is called from removing device; 1) is related to blkg, while 2) is not, hence refcnting from blkg can't fix the problem. refcnting from blkcg_policy_data should be ok, but I see that bfq already has the similar refcnting, while other policy doesn't require such refcnting. Any suggestions? Thanks, Kuai > Thanks. >