From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-178.mta1.migadu.com (out-178.mta1.migadu.com [95.215.58.178]) (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 D235B3914E1 for ; Thu, 9 Jul 2026 00:56:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.178 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783558605; cv=none; b=g2SUA4dhuYZxx114wzoe+uUdOdQP7qs57BTPS1v9JW2dP94xwdYBVRNeTInsVsFJzxJVw71h9fGwWdTE+Pf5aa5EEdTioL7RzFOXrXNEisurs0PsvIpSQ1q+3lkGdgcs41rcF4oWNwPd9LPJttF2D4KOBfDpgGjB3WAMGP1G0jQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783558605; c=relaxed/simple; bh=QW4SY9Z/tGn1IPNVvL7G7PC98wn1mtgzpnrzSAfXEx4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=u7Xc9f+UYPGCwvpDy5BPLYQwEfgheCAtqu/CfWodYaWSMzJ+3pb1KDKRCrrIpRpFGo8l+DxXuIl8dzffaKI1PiIluSycysj146rlIGMsOJdJNKS/+CP28Wp96rebAlcPEx0hp4+Iho9Rir843DpvgTatZs61nwlMWnuB4go0t9A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=ReY8dtSC; arc=none smtp.client-ip=95.215.58.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="ReY8dtSC" Message-ID: <8f74de0a-4c86-4da9-ad1b-3f496d3ab733@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1783558592; 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=QW4SY9Z/tGn1IPNVvL7G7PC98wn1mtgzpnrzSAfXEx4=; b=ReY8dtSCkspGxZ1EJpSTPWaK+F/2B5C0ODBysqxbKXH+vvH+AXFB3TW5zeIYMmj/NyL39w CBqzyLzl3gk3EQwZ0T+11DIsHmqRSwXb39b6NBJDiylvSESTKetbLGFFawc4ezjrrNlK/m nvdf44pCn4oHTkdIL2vpmZjbpDcZJTI= Date: Thu, 9 Jul 2026 08:56:13 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH 5.15.y 6.1.y 6.6.y 1/1] mm/vmscan: flush deferred TLB before freeing large folios To: Sasha Levin , stable@vger.kernel.org, linux-mm@kvack.org Cc: jiayuan.chen@shopee.com, yingfu.zhou@shopee.com, willy@infradead.org, Andrew Morton , Huang Ying , linux-kernel@vger.kernel.org References: <20260708041237.289026-2-jiayuan.chen@linux.dev> <20260708120502.agent5-0002@kernel.org> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Jiayuan Chen In-Reply-To: <20260708120502.agent5-0002@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 7/9/26 12:18 AM, Sasha Levin wrote: > On Wed, Jul 08, 2026 at 12:12:36PM +0800, Jiayuan Chen wrote: >> Flush the deferred batch before freeing a large folio inline, the same way >> the order-0 path already waits for the flush. > Queued for 6.6 and 6.1 with Matthew's Reviewed-by added, thanks. Thanks Sasha. >> destroy_compound_page was recently renamed to destroy_large_folio. >> So it would be conflict when this patch was applied to 5.15/6.1 > It actually applied cleanly to the current 6.1.y (that tree already > uses folio_test_large()/destroy_large_folio() there), but it does not > apply to 5.15.y, which is still page-based > (PageTransHuge()/destroy_compound_page()). Could you send a tested > per-branch version for 5.15.y? 5.10.y has the identical vulnerable code > shape, so a 5.10.y version would be welcome as well. I will try to reproduce and fix in 5.15 and 5.10.