From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C93D0C433FE for ; Mon, 28 Nov 2022 19:01:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233041AbiK1TBJ (ORCPT ); Mon, 28 Nov 2022 14:01:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233057AbiK1TBD (ORCPT ); Mon, 28 Nov 2022 14:01:03 -0500 Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0EB2E27B1F for ; Mon, 28 Nov 2022 11:00:58 -0800 (PST) Received: by mail-pj1-x1030.google.com with SMTP id l22-20020a17090a3f1600b00212fbbcfb78so14953492pjc.3 for ; Mon, 28 Nov 2022 11:00:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=LvEJDQxAkm5Pcp5ay5EjtKj5MIU+4aSru9VkuAAqDpI=; b=ZIxVcpTUMb/D5eaOHDEpksfQ3kJ7ZSLXnpj/xXuk9U3DX0xoA2fCl9AbKfhZwZhspV fbCcGlev/4EIGojtU1A9K3yvnZdq0T/YLnigSVlZGNQ4cmCpsz54dTGsTSZnzhQQSh2F Cfpm/jc+vFpNjyQ+IZMGe+5QzeVLYaYHfv1vY5263b/JPmEuMWLMhThQSjKqNuWjbaqr st2WSkGe+KfyQYa85gs07HW4jJt3Qgj8hCQALJ5ZvFw66ttA8YfEsaKse0X+lJHhwT/n JbSc9Xv4dAC1AUM24H/pg1KhjbiUnHTiPpNuNxguOTpswj0T3okv4RQZv7mFYqAHY8sd vCwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=LvEJDQxAkm5Pcp5ay5EjtKj5MIU+4aSru9VkuAAqDpI=; b=Wrdsukl6mMPOWr5DXD4lhMoRNfykAq7aH/ZYFGuWJg8lVZAqbijblhUnqETsV161o+ xJ/v5yWrBKSwqyDPeoS7oWEgwGCy0Df+7ueTNNsUGDRVyLxRZR+l1tBA2uInL5jpx9Bn t2RhChsgaf1cURb7I4vdHYuQG3b7iwJ21khR10J3oxwQN/CKAgV5isKVlfTUWtkFsXIq eIJS89YhQKwDhm+jEyku3KG3OzMPCgiGiXnzGRY8+1bOOKbwZNujBcaigGhnM7QzNQ4K 5/NIBzCxQr2yrlN+4vSZAEUr56BDJ/6Mos8pzIus/aOiAB96qbY0RoG23z+HGyJY9lHC Ccww== X-Gm-Message-State: ANoB5pnzIYMrSv+lnOO2CWh4Q604PiumuXUOsddd1LWytyuUPJwgnWpR K1Kc458yABRaVorXi+5TADhCwQ== X-Google-Smtp-Source: AA0mqf5Tp1M+FX2RI4vi6K/Uf4ycXTS0LenkHg91EgRKhSqajbSJM3Ugd/1SDVwIRupnNt7JPvregQ== X-Received: by 2002:a17:902:7d97:b0:188:f87d:70d3 with SMTP id a23-20020a1709027d9700b00188f87d70d3mr32810098plm.43.1669662058117; Mon, 28 Nov 2022 11:00:58 -0800 (PST) Received: from [192.168.1.136] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id oa16-20020a17090b1bd000b001ef8ab65052sm7929766pjb.11.2022.11.28.11.00.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Nov 2022 11:00:56 -0800 (PST) Message-ID: Date: Mon, 28 Nov 2022 12:00:55 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [PATCH-block] blk-cgroup: Use css_tryget() in blkcg_destroy_blkgs() Content-Language: en-US To: Bart Van Assche , Waiman Long , Tejun Heo Cc: cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Ming Lei , Andy Shevchenko , Andrew Morton , =?UTF-8?Q?Michal_Koutn=c3=bd?= , Hillf Danton , Yi Zhang References: <20221128033057.1279383-1-longman@redhat.com> From: Jens Axboe In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On 11/28/22 11:56 AM, Bart Van Assche wrote: > On 11/27/22 19:30, Waiman Long wrote: >> Fixes: 951d1e94801f ("blk-cgroup: Flush stats at blkgs destruction path") > > Has Jens' for-next branch perhaps been rebased? I see the following commit ID for that patch: > > dae590a6c96c ("blk-cgroup: Flush stats at blkgs destruction path") I don't know that sha is from, not from me. for-6.2/block has not been rebased, for-next gets rebased whenever I need to do so as linux-next is continually rebased anyway. But the sha for that commit would not change as a result. I don't even have that sha in my tree, so... -- Jens Axboe