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 90E133B9DAB; Mon, 14 Sep 2026 18:50:53 +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=1789411854; cv=none; b=gE5mYNjR3XR9AYsMuouyTBdMTYvqUl5EGeX+TN54yvwtytmGGaUx1XTPttSqj2jIumB+swgqAXa5lkzLmvT0NjhpOS+j8gFPawR08xyaKPvmGT9JaM/CvNB6pp3hpEnG/YKXCwXVXqHqQRRCZDUWIIwwG1dvFCtNpvZ7Rn+PLds= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789411854; c=relaxed/simple; bh=I9//0LB5K81ZQWzHLCCE2klREXKnr+J5NzqH0/mcr5A=; h=From:Subject:To:Cc:In-Reply-To:References:Content-Type:Date: Message-Id; b=dIPShaiwIaleMk4LVY3rVy6l366crzQROWoh24Jy8qFUkHKJdNu08dpJ+NHhZpfEP3yAzN5kZXRTL+BefuJAZcqL17kw0f1DPqDhfBKlS45fWaglMyt6HiB+B+EvjZwWhWxuD1WSL+SkFqUzJVZZryWCoIy9x6Ryv7iiiWvBg34= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=eVzMcghq; 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="eVzMcghq" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 429BD1F000FF; Mon, 14 Sep 2026 18:50:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1789411853; bh=I9//0LB5K81ZQWzHLCCE2klREXKnr+J5NzqH0/mcr5A=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=eVzMcghq8e9ClZddoNA5Ip+E/BeoV7jDyaXIiVIcm28dczlreWJBO0H/ZqBViXGSL VKrBwP1QJSkyTapOrXr185pObMtrnMYSaHCJDRtCaCzR/sJAdKSsY66JZWh2TrOPx1 jSPK5VXb4zdSANAwx/k6unl94prcRA0xmuhxHPKSXL9zoKYTh9qbhRi7vjpmkAHqzJ INsGPqEs2g+pQC2r0/8eGfUWf0ZeCtvOoGAAEqFY2RJ8nbi9GZhV2HilH6RzG1BfOL hPEXkJ6OpSrb9dJ0i57w8zCXGDqat4ORk2ewMXGa13pvgeceW10O2ANJDEYMSqAffe uXYeOA8FCPKJQ== From: sashiko-bot@kernel.org Subject: Re: [PATCH v2 15/40] mm/vma: add vma[_flags]_is_kernel_owned() predicates Reply-To: sashiko-reviews@lists.linux.dev To: =?utf-8?b?TG9yZW56byBTdG9ha2VzIChBUk0p?= Cc: linux-s390@vger.kernel.org, "Heiko Carstens" , linux-rdma@vger.kernel.org, kvm@vger.kernel.org, "Marc Zyngier" , "Alexander Gordeev" , dri-devel@lists.freedesktop.org, "Vasily Gorbik" , bpf@vger.kernel.org, "Christian Borntraeger" , linux-perf-users@vger.kernel.org, selinux@vger.kernel.org, linux-scsi@vger.kernel.org, kvmarm@lists.linux.dev, "Oliver Upton" , linux-trace-kernel@vger.kernel.org In-Reply-To: <20260914-b4-mmap-prepare-vma-flag-sanify-v2-15-7d9781ed5361@kernel.org> References: <20260914-b4-mmap-prepare-vma-flag-sanify-v2-0-7d9781ed5361@kernel.org> <20260914-b4-mmap-prepare-vma-flag-sanify-v2-15-7d9781ed5361@kernel.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Sep 2026 18:50:51 +0000 Message-Id: <20260914185052.429BD1F000FF@smtp.kernel.org> Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: > Rather than referring to VMA flags with uncertain meaning, add a new > predicate that explicitly describes what possession of the VMA_PFNMAP_BIT > or VMA_MIXEDMAP_BIT flags mean, and then refer to that function for > determining VMA mergeability. >=20 > Either flag means the contents of the mapping are owned by the kernel, > usually a driver, rather than by the core mm: the memory may be MMIO, > kernel-allocated pages or even ordinary pages the driver maps itself, but > the core must not populate, reclaim, migrate, copy-on-write or merge the > range on its own initiative. >=20 > We initially also include VMA_IO_BIT here, as by implication, these must = be > kernel-owned. (mlock() also sets VMA_IO_BIT transiently on ordinary VMAs > while locking them, which is addressed later in this series.) >=20 > However the intent is to in future remove this, as no mapping should be > marked as an I/O mapping without also being marked with VMA_PFNMAP_BIT. >=20 > This forms the basis of further work intended to improve how we express V= MA > properties such as this. >=20 > Also update the VMA userland tests to reflect the change. >=20 > No functional change intended. >=20 > Signed-off-by: Lorenzo Stoakes (ARM) Sashiko has reviewed this patch and found no issues. It looks great! --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20260914-b4-mmap-pr= epare-vma-flag-sanify-v2-0-7d9781ed5361@kernel.org?part=3D15