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 A180BC433FE for ; Mon, 28 Nov 2022 19:07:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232802AbiK1TH5 (ORCPT ); Mon, 28 Nov 2022 14:07:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38640 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232932AbiK1THy (ORCPT ); Mon, 28 Nov 2022 14:07:54 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4F13BE12; Mon, 28 Nov 2022 11:07:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1669662474; x=1701198474; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=6IzE0TtuysAfUgoGUzezLoeld/EU8Trm4OQzeKfJ5oc=; b=nC33FJv7I7UUaafnwb7gtU7gcd48/D3HXD7kM70PnQwFq+a5WKgQFVmf Qpoeq4d2z6WFa4f0I/AqYXkVjmLpLwlSX31SojKnBh8zXofcvsKOYfQI2 L5Y9XXy9t/MS7VTLzPP4JVohyx37lDBvaJEI1zZ+F2c0JJSA97uz+9xmG LYvax2PhFRDzixRdQxvQdIGxqot3lVmY+HOWFeGb0yqqWqAO3qO5+/2am v+BEpiNcjojt7fmIIUcixlr8yD9MzX6MfAKMFF4ywf+V+cBRJnkwbBFle 4l51rj/RN1KVL2VgjQTpqG4Z3FcF5rHQ4nGovhO0wkDuA+PDhRcANyn/3 w==; X-IronPort-AV: E=McAfee;i="6500,9779,10545"; a="295305434" X-IronPort-AV: E=Sophos;i="5.96,200,1665471600"; d="scan'208";a="295305434" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Nov 2022 11:07:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10545"; a="706908914" X-IronPort-AV: E=Sophos;i="5.96,200,1665471600"; d="scan'208";a="706908914" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga008.fm.intel.com with ESMTP; 28 Nov 2022 11:07:34 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ozjTY-001MMc-2n; Mon, 28 Nov 2022 21:07:32 +0200 Date: Mon, 28 Nov 2022 21:07:32 +0200 From: Andy Shevchenko To: Jens Axboe Cc: Bart Van Assche , Waiman Long , Tejun Heo , cgroups@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Ming Lei , Andrew Morton , Michal =?iso-8859-1?Q?Koutn=FD?= , Hillf Danton , Yi Zhang Subject: Re: [PATCH-block] blk-cgroup: Use css_tryget() in blkcg_destroy_blkgs() Message-ID: References: <20221128033057.1279383-1-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Mon, Nov 28, 2022 at 12:00:55PM -0700, Jens Axboe wrote: > 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... $ git tag --contains dae590a6c96c next-20221117 next-20221118 next-20221121 next-20221122 next-20221123 next-20221124 next-20221125 next-20221128 -- With Best Regards, Andy Shevchenko