From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4A51E239E65 for ; Tue, 23 Dec 2025 01:59:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766455198; cv=none; b=btJiSuixZDEczv+NB4LM1a5fxlzG7hCAiOdR5HnIvMwdkhS5JG7uaD9j7VF/SNxzftYJzLUkLm9VPF3FwF7yVZKoe5wDPxWNHbfyAKI1Nt9LD7CXo9G0yj8jF9lUqCnQIP1qjRi5C6rBAL9WQn7eeK3QONumUhdigq2f4EOjwWw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766455198; c=relaxed/simple; bh=yV8XQYnghuYhjxnB+j4OdCi0iKmCmzJq8LuQA5bIn6I=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=bkFpFzOKvzOEeI15ieVNoboumwf4SnFgxa8plOyEDCCzrZjtqwMEoyTSINKsV9f6NNDP/WuMub1Gkgi/JyBxrk3/NqtPO52rUMkVMHgCmhkddC1V/hwvG4aSvrIM4Ku4xkIkxm3heDQNkLCxbx6Tmc/rFWIQt1FHEbIFM/r5ZXw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=ULctXWJb; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="ULctXWJb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9767FC4CEF1; Tue, 23 Dec 2025 01:59:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1766455197; bh=yV8XQYnghuYhjxnB+j4OdCi0iKmCmzJq8LuQA5bIn6I=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ULctXWJbVUAAGZMDutAkeqpU+T2GHmh030Kod3ExAXEDCQ2yJYeilyS7QEbN3n93A YSRVTqHXXfyriW3g118ZEH19wtan0CBV5iVm1AiGre09wqhmbNMSADIKXeaIxId7h3 35EHAcV9dF9BVmHBLlOQgHT09WZ/XfcDxzEBHOM8= Date: Mon, 22 Dec 2025 17:59:57 -0800 From: Andrew Morton To: Mathieu Desnoyers Cc: linux-kernel@vger.kernel.org, Mark Brown , linux-mm@kvack.org Subject: Re: [PATCH v1 0/5] MM_CID and HPCC mm_struct static init fixes Message-Id: <20251222175957.bfc9cf8b25e587f3f5e304bc@linux-foundation.org> In-Reply-To: <20251221232926.450602-1-mathieu.desnoyers@efficios.com> References: <20251221232926.450602-1-mathieu.desnoyers@efficios.com> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sun, 21 Dec 2025 18:29:21 -0500 Mathieu Desnoyers wrote: > Mark Brown reported a regression [1] on linux next due to the > hierarchical percpu counters (HPCC). You mentioned they were only in > mm-new (and therefore not pulled into -next) [2], but it looks like they > got more exposure that we expected. :) We try to please ;) Mark's report is why this series remains in mm-new and didn't get promoted to mm-unstable (and hence linux-next). Also, I anticipate a new version of this series thanks to https://lkml.kernel.org/r/2fb78e41-5e56-425f-925f-a29524355d2c@efficios.com > This bug hunting got me to fix static initialization issues in both > MM_CID (for upstream) and HPCC (mm-new). Mark tested my series and > confirmed that it fixes his issues. > > Please consider the HPCC fixes for mm-new, and the MM_CID fixes for > upstream. > > This series is based on mm-new > commit 287373d0b6ee ("selftests/mm: fix comment for check_test_requirements") Well, simply appending this series to your "mm: Fix OOM killer inaccuracy on large many-core systems, v10" will create an annoying bisection hole. Also, there are some cc:stable fixes in here which depend upon the presence of "mm: Fix OOM killer inaccuracy on large many-core systems" series, which is all backwards. So for now I'll toss this series in there for testing but I'll ask for a redo, please. - All cc:stable patches prepared in a standalone fashion against latest mainline. - Any non-cc:stable patches which fix things in current mm-new come next. Perhaps view these as preparation for "mm: Fix OOM killer inaccuracy on large many-core systems". - Then "mm: Fix OOM killer inaccuracy on large many-core systems, v11" which incorporates anything which didn't make it into the above two categories. That could be as many as three patch series. Thanks.