From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793724369; b=as5SZHjLuiUTVuVtUuDX327WlcRrXzJU1kCnpwpp95IxxhzzlQf8ozh9ghwWOAmcJTbv 3OHvQgQ5N7m4yMCJF20E8yZottsd8buhdN4gKIv1CoSRrubP9x5+XSZnijYvseQEIJHUj +8EvUwd8WhYXw8ZpTdIVWTaftqJt9ZxlvvBrGbaZAE+mLal6JHm74+kLryWS3lxxRRY3p CSmRuXq+f1/MzvKcNNkV47Y7joEH7CPS8XBxALwNrMW5m1Nj8OKRRGZstPBsOp6hvCNvl L6d+XJumVi1sy3YdZbD+5KV3R57vK2gPl5RQtA8n+hjliwtiHWqOBQzbrTKKzwqXE1Q== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793724369; h=DMARC-Filter:DKIM-Signature:Received:X-MC-Unique: X-Mimecast-MFC-AGG-ID:Received:Received:Message-ID:Date:MIME-Version: User-Agent:Subject:To:Cc:References:Content-Language:From:In-Reply-To: Content-Type:Content-Transfer-Encoding:X-Scanned-By; bh=QrQxpAgOB38zPWPykzyeyLu30lUbfa9ddi7dGDk1YNA=; b=J/xGzkwa0aJkML/AjcKaplvC0m5dtBK24g0Un2ETAY1Z7a3H7kuPFeawcB10edo2H0af x8opQQnqVUXbysAjDl8IAZEWKCg0G2tRK8iNq8zEUiMlk4Imi1GXoK1K+Q4q4gFb2mulX 2UUphKE2eaa2rk0XZGELLIAMa+Kv3R9w6S4x768hx/iK5hAnFp+Y/ratOZhj02z+olQbY nunzTAvpkKpWD0eYeU1l+ju0+mDyI0S3M0A/flZvDLbpGKvBDRDzPqgpUPHobbDhACYH0 4ZrIT5jjgvbqf/n0TDRfeJM7tcXhoBqPwZdm2mzvkbKmh7czDawXJemRF5Z416En9Mw== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=TvtiSkeN; arc=none smtp.remote-ip=170.10.133.124 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BE26B606A324 for ; Tue, 3 Nov 2026 16:46:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org BE26B606A324 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=TvtiSkeN DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1793724367; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QrQxpAgOB38zPWPykzyeyLu30lUbfa9ddi7dGDk1YNA=; b=TvtiSkeNc4Prefz3cn4mDX8TtiYzM6ybmoaWhLDMhBCSx7VvDXxH9X1ouVNR+cWeuJ4hqL 2jWqVhoEm+JZ7cH926g/FalbRQZVdPflzRHJ5Nbre9J78OPob0GbYwXk+byRyZCiSrDrP+ HbELGc7zXlLcQUCtXZgtSuZkceNjEM0= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-668-inK9B4OPMa6z1NdhMIdAQg-1; Tue, 03 Nov 2026 11:46:05 -0500 X-MC-Unique: inK9B4OPMa6z1NdhMIdAQg-1 X-Mimecast-MFC-AGG-ID: inK9B4OPMa6z1NdhMIdAQg_1793724363 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 1BB3319560B7; Tue, 3 Nov 2026 16:46:03 +0000 (UTC) Received: from [100.91.18.181] (headnet04.pony-001.prod.iad2.dc.redhat.com [10.2.32.116]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 734531955F43; Tue, 3 Nov 2026 16:46:01 +0000 (UTC) Message-ID: <33024a13-9706-486c-aef0-aeeb2193c8ee@redhat.com> Date: Tue, 3 Nov 2026 11:46:00 -0500 X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 0/3] cgroup/cpuset: Fix some more bugs in cpuset partition code To: Tejun Heo Cc: Ridong Chen , Johannes Weiner , =?UTF-8?Q?Michal_Koutn=C3=BD?= , Shuah Khan , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, Guopeng Zhang References: <20261030190701.78308-1-longman@redhat.com> <886a562b52b1c5094142d547a8336457@kernel.org> Content-Language: en-US From: Waiman Long In-Reply-To: <886a562b52b1c5094142d547a8336457@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 On 11/2/26 3:04 AM, Tejun Heo wrote: >> cgroup/cpuset: Fix incorrect CPU accounting with parent's >> effective_xcpus expansion >> cgroup/cpuset: Recompute effective cpumask in update_cpumasks_hier() >> after calling update_parent_effective_cpumask() >> cgroup/cpuset: Do housekeeping check when isolated child with root >> parent may get more xcpus > Applied 1-3 to cgroup/for-7.4-fixes with the following tags added: > > Reviewed-by: Guopeng Zhang > Tested-by: Guopeng Zhang > > Two issues I noticed: > > - Three of patch 1's new TEST_MATRIX rows end with A1 as a single-CPU > root partition, which has no sched domain, so they fail the ISOLCPUS > check when the script runs with -v. > > - The comment at the end of the "partcmd_update w/o newmask" block in > update_parent_effective_cpumask() still says there is no need to > adjust the parent's effective_cpus. Patch 1's new expansion branch now > does exactly that. Thanks for noticing that. Will fix that in the next set of fixes that I am working on. Cheers, Longman