From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794677522; b=0zRtqv5+6ARyLIvKzS0Ha2NdeCjcJXrewOWwKiwGFDdN0fVgHVbChdkkPNa9Va+Q7DoJ J9/PtT65OX4EtXDGdu3kCg/Neqewft58+Fu1NvZU8UZpHutXWuSJbc7ItBarT2sPoYxDD qDq2sWwmqplZPAOd/m8o5DxEgttz7Mp+SWUNoow8fhG6hVe5qpqi6YsuBCEbxwF01uBG2 s1S/xPjOrTSknWwkynVg0W2R6Nqis7G+7eI1cPUCdHoBCn4xv08yP/qRc59LwLJpdsnO4 xq8D37xlERcKtKUi/rLQ+asij6anyQCyZig8A7YEr1mKqWcxrZqxZ4mGCCbRK4CS3tQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794677522; h=Received:DKIM-Signature:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; bh=AljFBfIqcD1ZWecoMIIEjM2yrPFU4geEAa8J3J+RzSI=; b=Tz+OKAkweab0lhCbgSR0kw0W6r/wA7Po6PBYSuz2LrpWzyZDPCKF1iO2Z60pOFAn1M7m MnSjMrcVra6ikzvKCfJQDzwreSzcVOn7TwJ2K3rKPO0/6q0Z/ubm8syas/aKVZz8NEsUz FL1HZEWzS81OKo3Pr1LgfANzhpuiF3BflwnzTyCjg6BBwkY++HHWzzKRD7Q/tAmbdOnTY 7KyhLVpBryjSuAcOvqbTG1q4DSWYM+YxGQs4/8Z3F6/9eFSflXQXOl9ykDTTYSvqPkE+F ++a5rN4Slz0Ps9MTNBZUqe0oWuu9SgAPR1yGfsojTDGN7eHH3N6Fgfo0wUjO/UVsoMg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=ObqNUb3r; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 429D2606A327; Sat, 14 Nov 2026 17:32:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20260515 header.b=ObqNUb3r Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0F9E01F000C4; Sat, 14 Nov 2026 17:31:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1794677521; bh=AljFBfIqcD1ZWecoMIIEjM2yrPFU4geEAa8J3J+RzSI=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ObqNUb3rKiS4yM6Gx8oWG4UUqxI61uIvOXGmQ5kWt6uCoyS6klGsYFAfIFeZjQK7Z WmodSxBw2K8Gc7zgtTpEDad5gKA+SXjpbSL8F36t3CGb2c9u4LYPinBOj4tluVSh8g cZNAV50PT6+QvQFvppbopy9lIinxs1Sq3vyZ2U62s7bmDVYWa6bHKnsrOO/pBVabK/ myCdflNoBM5deUNg0EcV2g+NndbsfDXCR/xJalleom0x3NppP8fBJXFETJ/msTOljp jV9gpvzRpQTmen093PZThK7Lmzd9W7rA1CFZAobft/EkWhvP1vxu2BOxJUvMb523HW 3bH9Z8rz1R7PQ== Date: Sat, 14 Nov 2026 17:31:57 +0000 From: "Lorenzo Stoakes (ARM)" To: shao.mingyin@zte.com.cn Cc: akpm@linux-foundation.org, david@kernel.org, linux-mm@kvack.org, virtualization@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/balloon: fix NR_BALLOON_PAGES accounting on migration failure Message-ID: References: <20261115004708909xx05JgB9nXnOCG0zL7h_K@zte.com.cn> X-Mailing-List: virtualization@lists.linux.dev List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20261115004708909xx05JgB9nXnOCG0zL7h_K@zte.com.cn> On Sun, Nov 15, 2026 at 12:47:08AM +0800, shao.mingyin@zte.com.cn wrote: > From: Shao Mingyin > > mm/balloon: fix NR_BALLOON_PAGES accounting on migration failure > > A balloon driver's -ENOENT migration result means that the old page was > deflated but the replacement was not inflated. vmw_balloon returns this > when its deflate operation succeeds and the subsequent inflate fails. > > balloon_page_migrate() accounts the deflation and frees the old page, > but does not decrement NR_BALLOON_PAGES. Each such failure therefore > leaves one extra page in the per-node count, which also contributes to > the Balloon value in /proc/meminfo. > > Decrement the counter on the old page's node, matching normal dequeue > accounting. > > Fixes: 4d689474e1b2 ("balloon_compaction: update the NR_BALLOON_PAGES state") > Signed-off-by: Shao Mingyin NAK. this is generated by some AI slopper's script, spamming the kernel. The patches I looked at were wrong/broken, so no to anything from this person. They've sent 300 mails in under four weeks spanniing: ata, scsi, target, ufs, nvme/nvmet, ubifs, ublk, zloop, dm, md, mmc, virtio-blk, mfd, gpio, pwm, spi, PCI, ASoC, ACPI, net, vfs mount, block partitions, and now mm. and 17 series across 7 subsystems over the past 23 hours. We need a way to ban emails from people like this... -- Cheers, Lorenzo