From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 4C2B0298CC4 for ; Wed, 22 Jul 2026 11:52:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784721160; cv=none; b=T0HGqTkEr+9n6K7XeORRK+GsPOUWdIix57pny8rN84olQnLCyBn+we3SwlS0T5efXxUtiwi7QsB61pT0IYdJXZbQj7a49b3vTyH02mI0+WKLC0+mc4WzsVW0cKPk2PsEWVGD4eC2i/4jpAlRoVSuH9TxCQqledjHHEEt9tPgxZs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784721160; c=relaxed/simple; bh=W4KpWLL9tuHSaapZgogLQlkYlHzc427RYgqGMz4ynzo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YPIZNh+Wpn31PkAzOKHx+xqYAUkq8ubbazurvKCBQqYn/EiKgd5om2/dTx0ehovD80e4M3ZKYymos/tAtLd/lZW9wsU0Y3PvaknV2qM/to/eCi+EuYJyWL4yoZQssQrrwhoJDVrMJeZvmBmeXLCrHp/wk18iL7QcTfjLtQwCvuM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=IsbXT4SE; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="IsbXT4SE" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 779D91F000E9; Wed, 22 Jul 2026 11:52:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784721158; bh=2u+YmL3O7mDZg1oLXMa5OhmXTCMV452YGb8AVhTqv5A=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=IsbXT4SEjVnkwnCXzJY0T8cBl50BCSrCVGmwo9Gs3OAFL2HC7CMfLRTz+kXbHM+7u +TRC1/3Wj1Vtu8B027gT6rpfd6xraxlmp6/frHM92cIjrOqKI/W8uhmkW0CA1+BuGc LH/JD5egHL5o5LeOzFq0FxEMgPAaBVOIgqYsGSldxCIw6WZCTxTn/IEIVm7xi+aV3Y bkZULNGGTO1WdMjMmYK2M4kUik3xFZb0Vhyp/ovpdVvWTE3hjV2AY2pKylyN8I0bD1 ahInEjp8GrtjzJqlw8gqwZAFNB8cAPZ6Lf63qQZmM130cQK/Y5UdMF70oeXuFfTkcN iW7ODO9zjcEXw== Date: Wed, 22 Jul 2026 12:52:29 +0100 From: Will Deacon To: Dev Jain Cc: Andrew Morton , muchun.song@linux.dev, osalvador@suse.de, ljs@kernel.org, david@kernel.org, liam@infradead.org, catalin.marinas@arm.com, kernel-team@android.com, riel@surriel.com, vbabka@kernel.org, harry@kernel.org, jannh@google.com, lance.yang@linux.dev, kas@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, apopple@nvidia.com, rcampbell@nvidia.com, ziy@nvidia.com, matthew.brost@intel.com, joshua.hahnjy@gmail.com, rakie.kim@sk.com, byungchul@sk.com, gourry@gourry.net, ying.huang@linux.alibaba.com, ak@linux.intel.com, nao.horiguchi@gmail.com, mel@csn.ul.ie, j-nomura@ce.jp.nec.com, pfalcato@suse.de, tglx@kernel.org, dave.hansen@intel.com, jpoimboe@kernel.org, linux-arm-kernel@lists.infradead.org, ryan.roberts@arm.com, anshuman.khandual@arm.com Subject: Re: [PATCH v3 0/6] Fix incorrect access of hugetlb pte entries Message-ID: References: <20260703114202.365553-1-dev.jain@arm.com> <178464737122.1305746.12295190523058911270.b4-ty@kernel.org> <20260721133636.df1a012df895054d3fd34a2e@linux-foundation.org> <4bb234f7-5f3a-452d-92dd-a1e62b6f39aa@arm.com> 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-Disposition: inline In-Reply-To: <4bb234f7-5f3a-452d-92dd-a1e62b6f39aa@arm.com> On Wed, Jul 22, 2026 at 10:03:04AM +0530, Dev Jain wrote: > @Will if you could edit the commit message with the following userspace visible > effect: > > "On systems where CONT_PTES != CONT_PMDS (meaning page size is 16K), we could collect > excess a/d bit state, meaning extra work for the kernel. Even worse, we may iterate > beyond the PTE table and dereference a garbage ptep pointer to access physical > memory we don't own. Since the ptep pointer is a linear map address, we may run off > the end of the linear map, dereference a VA not mapped into the kernel pgtables and > cause kernel panic." It's sitting on top of for-next/fixes so I can fold that in, thanks. Will