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=1795170999; b=u/Rg6Gh4nzirK9KQ/pcG8PE0M1h0HaZ2uCNhZePL6QOjYexP3+p5d8QUr6EySuwz85FB GsdFnVpJILG6Q/0E1TadIwcWsbwWxbRcIa2s+B+v09GNowzhydLIgiqEX5h6+9fD832oF I2ihnqQ/SUb5Urr7bPyIcjQBv1f/1O0BfUAFngPh84HSEZiJWorfgnp7uN4Z/wNrFr38F JWHdSfkZZmQq2oYMQIabRj2sNRuk2B3oY/zVG4NBeP39lknZFdPdIjhMELUSI+DHXS6Bj ipeN0K+4enCuHSZKUWQfTR/+qtvgZL2EkyT5jwh5mCNTy7bv1X2ePbtorhy9AcG0mxw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795170999; h=Received:DKIM-Signature:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; bh=OBbEyP/H6djxrJo03P55CCCJILRL7MXtwftvePmw9sQ=; b=nv5RdHqdyuplb+cSZOjcKcS6yQd67hAliY11Cf0C8oIl8CgdCpiGlpIiWgNjiPt42kxY rHQauFHvWN5uugveXkJGTxx/nPRX4BLV7ygqGAA2G7OZBDnaFxY4zPZWdK6B4BJ4u1p8a QsiXd3SBC24bCw1S2Wcz9TtCn70WBOqYQR62ul/tNCPqr/t3p6HOFv2esRi3APJX/Nz62 +3Ku8JwvgHgeVl2UIcNCjotSpoiVzem+t1lMXVodVVjE1KQkCkjV7OcYAjek9C0slYak8 VpC/TYbROehUyoeuB575rUun7JdZp5WBuIyJDoYfqzRRve+ofMeWmNY+PSLB3OU2PSg== 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=NqYTjW+h; 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 3EF25606A325; Fri, 20 Nov 2026 10:36:38 +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=NqYTjW+h Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C85D1F000C6; Fri, 20 Nov 2026 10:36:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1795170998; bh=OBbEyP/H6djxrJo03P55CCCJILRL7MXtwftvePmw9sQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=NqYTjW+hRZedNoLan48YbMHilMOqdxA6SvuPNs27BdYAJtMieE3b+p88qlC0nltBB dKXeSnrN0Ai0EUxJOQPnJ08kxNl9XL5rXMHb6+ul/GWzw/SWMIHxWj2ENcIOAH+hw0 VG0b6+k1zpQx25ACmN44hZt0lyQABY4JM+N+BzaVBEA3dfT6Lc9rBBGWjDO5J6ZMst hHsY6Be0hY2pKTeiR75KILAhbrgWhWpjDEnKrsUmyeq4DxKZQWegGyYXhtBJOLkwjQ vPrNR05u216qwRlxj5CK8Ti3YFnayv1KeFvoQxn0SgTKyPVu/3xmbO8jPRbaV1gML1 lWT3/zctQXpVA== Date: Fri, 20 Nov 2026 10:36:35 +0000 From: "Lorenzo Stoakes (ARM)" To: "David Hildenbrand (Arm)" Cc: shao.mingyin@zte.com.cn, akpm@linux-foundation.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> <96462da9-9437-4774-a5c7-f99858481ece@kernel.org> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <96462da9-9437-4774-a5c7-f99858481ece@kernel.org> On Fri, Nov 20, 2026 at 10:59:47AM +0100, David Hildenbrand (Arm) wrote: > On 11/14/26 18:31, Lorenzo Stoakes (ARM) wrote: > > 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... > > Yeah, that's absolutely annoying. In particular as we REQUIRE people to > understand the changes they submit, and own the code. > > That clearly won't happen in this case. > > There is a real (low prio) bug hiding in there, so something to be fixed. I'll > take care of it. > > I'll take care of it. Ack, yeah, I think the best approach is to treat these as reports, and if there's anything valid pull that out for a member of the core team :) -- Cheers, Lorenzo