All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com,
	vbabka@suse.cz,  hannes@cmpxchg.org, mgorman@techsingularity.net,
	dave@stgolabs.net,  willy@infradead.org, liam.howlett@oracle.com,
	peterz@infradead.org,  ldufour@linux.ibm.com, paulmck@kernel.org,
	luto@kernel.org,  songliubraving@fb.com, peterx@redhat.com,
	david@redhat.com,  dhowells@redhat.com, hughd@google.com,
	bigeasy@linutronix.de,  kent.overstreet@linux.dev,
	punit.agrawal@bytedance.com, lstoakes@gmail.com,
	 peterjung1337@gmail.com, rientjes@google.com,
	axelrasmussen@google.com,  joelaf@google.com, minchan@google.com,
	jannh@google.com, shakeelb@google.com,  tatashin@google.com,
	edumazet@google.com, gthelen@google.com,  gurua@google.com,
	arjunroy@google.com, soheil@google.com,  hughlynch@google.com,
	leewalsh@google.com, posk@google.com, will@kernel.org,
	 aneesh.kumar@linux.ibm.com, npiggin@gmail.com,
	chenhuacai@kernel.org,  tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de,  dave.hansen@linux.intel.com, richard@nod.at,
	anton.ivanov@cambridgegreys.com,  johannes@sipsolutions.net,
	qianweili@huawei.com, wangzhou1@hisilicon.com,
	 herbert@gondor.apana.org.au, davem@davemloft.net,
	vkoul@kernel.org,  airlied@gmail.com, daniel@ffwll.ch,
	maarten.lankhorst@linux.intel.com,  mripard@kernel.org,
	tzimmermann@suse.de, l.stach@pengutronix.de,
	 krzysztof.kozlowski@linaro.org, patrik.r.jakobsson@gmail.com,
	 matthias.bgg@gmail.com, robdclark@gmail.com,
	quic_abhinavk@quicinc.com,  dmitry.baryshkov@linaro.org,
	tomba@kernel.org, hjc@rock-chips.com,  heiko@sntech.de,
	ray.huang@amd.com, kraxel@redhat.com, sre@kernel.org,
	 mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
	tfiga@chromium.org,  m.szyprowski@samsung.com,
	mchehab@kernel.org, dimitri.sivanich@hpe.com,
	 zhangfei.gao@linaro.org, jejb@linux.ibm.com,
	martin.petersen@oracle.com,  dgilbert@interlog.com,
	hdegoede@redhat.com, mst@redhat.com,  jasowang@redhat.com,
	alex.williamson@redhat.com, deller@gmx.de,  jayalk@intworks.biz,
	viro@zeniv.linux.org.uk, nico@fluxnic.net,  xiang@kernel.org,
	chao@kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
	 miklos@szeredi.hu, mike.kravetz@oracle.com,
	muchun.song@linux.dev,  bhe@redhat.com, andrii@kernel.org,
	yoshfuji@linux-ipv6.org,  dsahern@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, perex@perex.cz,  tiwai@suse.com,
	haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
	 linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	 linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	 linux-graphics-maintainer@vmware.com,
	linux-ia64@vger.kernel.org,  linux-arch@vger.kernel.org,
	loongarch@lists.linux.dev, kvm@vger.kernel.org,
	 linux-s390@vger.kernel.org, linux-sgx@vger.kernel.org,
	 linux-um@lists.infradead.org, linux-acpi@vger.kernel.org,
	 linux-crypto@vger.kernel.org, nvdimm@lists.linux.dev,
	 dmaengine@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	 dri-devel@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
	 linux-samsung-soc@vger.kernel.org,
	intel-gfx@lists.freedesktop.org,
	 linux-mediatek@lists.infradead.org,
	linux-arm-msm@vger.kernel.org,  freedreno@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org,  linux-tegra@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	 xen-devel@lists.xenproject.org,
	linux-stm32@st-md-mailman.stormreply.com,
	 linux-rdma@vger.kernel.org, linux-media@vger.kernel.org,
	 linux-accelerators@lists.ozlabs.org, sparclinux@vger.kernel.org,
	 linux-scsi@vger.kernel.org, linux-staging@lists.linux.dev,
	 target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
	 netdev@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-aio@kvack.org,  linux-fsdevel@vger.kernel.org,
	linux-erofs@lists.ozlabs.org,  linux-ext4@vger.kernel.org,
	devel@lists.orangefs.org,  kexec@lists.infradead.org,
	linux-xfs@vger.kernel.org, bpf@vger.kernel.org,
	 linux-perf-users@vger.kernel.org, kasan-dev@googlegroups.com,
	 selinux@vger.kernel.org, alsa-devel@alsa-project.org,
	kernel-team@android.com,  surenb@google.com
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com,
	vbabka@suse.cz,  hannes@cmpxchg.org, mgorman@techsingularity.net,
	dave@stgolabs.net,  willy@infradead.org, liam.howlett@oracle.com,
	peterz@infradead.org,  ldufour@linux.ibm.com, paulmck@kernel.org,
	luto@kernel.org,  songliubraving@fb.com, peterx@redhat.com,
	david@redhat.com,  dhowells@redhat.com, hughd@google.com,
	bigeasy@linutronix.de,  kent.overstreet@linux.dev,
	punit.agrawal@bytedance.com, lstoakes@gmail.com,
	 peterjung1337@gmail.com, rientjes@google.com,
	axelrasmussen@google.com,  joelaf@google.com, minchan@google.com,
	jannh@google.com, shakeelb@google.com,  tatashin@google.com,
	edumazet@google.com, gthelen@google.com,  gurua@google.com,
	arjunroy@google.com, soheil@google.com,  hughlynch@google.com,
	leewalsh@google.com, posk@google.com, will@kernel.org,
	 aneesh.kumar@linux.ibm.com, npiggin@gmail.com,
	chenhuacai@kernel.org,  tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de,  dave.hansen@linux.intel.com, richard@nod.at,
	anton.ivanov@cambridgegreys.com,  johannes@sipsolutions.net,
	qianweili@huawei.com, wangzhou1@hisilicon.com,
	 herbert@gondor.apana.org.au, davem@davemloft.net,
	vkoul@kernel.org,  airlied@gmail.com, daniel@ffwll.ch,
	maarten.lankhorst@linux.intel.com,  mripard@kernel.org,
	tzimmermann@suse.de, l.stach@pengutronix.de,
	 krzysztof.kozlowski@linaro.org, patrik.r.jakobsson@gmail.com,
	 matthias.bgg@gmail.com, robdclark@gmail.com,
	quic_abhinavk@quicinc.com,  dmitry.baryshkov@linaro.org,
	tomba@kernel.org, hjc@rock-chips.com,  heiko@sntech.de,
	ray.huang@amd.com, kraxel@redhat.com, sre@kernel.org,
	 mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
	tfiga@chromium.org,  m.szyprowski@samsung.com,
	mchehab@kernel.org, dimitri.sivanich@hpe.com,
	 zhangfei.gao@linaro.org, jejb@linux.ibm.com,
	martin.petersen@oracle.com,  dgilbert@interlog.com,
	hdegoede@redhat.com, mst@redhat.com,  jasowang@redhat.com,
	alex.williamson@redhat.com, deller@gmx.de,  jayalk@intworks.biz,
	viro@zeniv.linux.org.uk, nico@fluxnic.net,  xiang@kernel.org,
	chao@kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
	 miklos@szeredi.hu, mike.kravetz@oracle.com,
	muchun.song@linux.dev,  bhe@redhat.com, andrii@kernel.org,
	yoshfuji@linux-ipv6.org,  dsahern@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, perex@perex.cz,  tiwai@suse.com,
	haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
	 linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	 linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	 linux-graphics-maintainer@vmware.com,
	linux-ia64@vger.kernel.org,  linux-arch@vger.kernel.org,
	loongarch@lists.linux.dev, kvm@vger.kernel.org,
	 linux-s390@vger.kernel.org, linux-sgx@vger.kernel.org,
	 linux-um@lists.infradead.org, linux-acpi@vger.kernel.org,
	 linux-crypto@vger.kernel.org, nvdimm@lists.linux.dev,
	 dmaengine@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	 dri-devel@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
	 linux-samsung-soc@vger.kernel.org,
	intel-gfx@lists.freedesktop.org,
	 linux-mediatek@lists.infradead.org,
	linux-arm-msm@vger.kernel.org,  freedreno@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org,  linux-tegra@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	 xen-devel@lists.xenproject.org,
	linux-stm32@st-md-mailman.stormreply.com,
	 linux-rdma@vger.kernel.org, linux-media@vger.kernel.org,
	 linux-accelerators@lists.ozlabs.org, sparclinux@vger.kernel.org,
	 linux-scsi@vger.kernel.org, linux-staging@lists.linux.dev,
	 target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
	 netdev@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-aio@kvack.org,  linux-fsdevel@vger.kernel.org,
	linux-erofs@lists.ozlabs.org,  linux-ext4@vger.kernel.org,
	devel@lists.orangefs.org,  kexec@lists.infradead.org,
	linux-xfs@vger.kernel.org, bpf@vger.kernel.org,
	 linux-perf-users@vger.kernel.org, kasan-dev@googlegroups.com,
	 selinux@vger.kernel.org, alsa-devel@alsa-project.org,
	kernel-team@android.com,  surenb@google.com
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, nvdimm@lists.linux.dev, heiko@sntech.de,
	leewalsh@google.com, dri-devel@lists.freedesktop.org,
	perex@perex.cz, jglisse@google.com, arjunroy@google.com,
	m.szyprowski@samsung.com, linux-arch@vger.kernel.org,
	qianweili@huawei.com, linux-samsung-soc@vger.kernel.org,
	aneesh.kumar@linux.ibm.com, chenhuacai@kernel.org,
	kasan-dev@googlegroups.com, linux-acpi@vger.kernel.org,
	rientjes@google.com, xen-devel@lists.xenproject.org,
	devel@lists.orangefs.org, robdclark@gmail.com,
	minchan@google.com, robert.jarzmik@free.fr,
	linux-um@lists.infradead.org, etnaviv@lists.freedesktop.org,
	npiggin@gmail.com, alex.williamson@redhat.com,
	viro@zeniv.linux.org.uk, luto@kernel.org, gthelen@google.com,
	tglx@linutronix.de, ldufour@linux.ibm.com, surenb@google.com,
	linux-sgx@vger.kernel.org, martin.petersen@oracle.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-media@vger.kernel.org,
	freedreno@lists.freedesktop.org, joelaf@google.com,
	linux-aio@kvack.org, linux-fbdev@vger.kernel.org,
	linux-ia64@vger.kernel.org, david@redhat.com,
	dave.hansen@linux.intel.com,
	virtualization@lists.linux-foundation.org, edumazet@google.com,
	target-devel@vger.kernel.org, punit.agrawal@bytedance.com,
	linux-s390@vger.kernel.org, dave@stgolabs.net, deller@gmx.de,
	hughd@google.com, andrii@kernel.org,
	patrik.r.jakobsson@gmail.com,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-rockchip@lists.infradead.org,
	linux-graphics-maintainer@vmware.com, kernel-team@android.com,
	jayalk@intworks.biz, soheil@google.com, selinux@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, mripard@kernel.org,
	shakeelb@google.com, haojian.zhuang@gmail.com,
	loongarch@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	tytso@mit.edu, nico@fluxnic.net, muchun.song@linux.dev,
	hjc@rock-chips.com, mcoquelin.stm32@gmail.com,
	tatashin@google.com, mike.kravetz@oracle.com,
	songliubraving@fb.com, jasowang@redhat.com,
	alsa-devel@alsa-project.org, peterx@redhat.com,
	linux-tegra@vger.kernel.org, kraxel@redhat.com, will@kernel.org,
	dmaengine@vger.kernel.org, bhe@redhat.com, miklos@szeredi.hu,
	linux-rdma@vger.kernel.org, linux-staging@lists.linux.dev,
	willy@infradead.org, gurua@google.com, dgilbert@interlog.com,
	xiang@kernel.org, pabeni@redhat.com, jejb@linux.ibm.com,
	quic_abhinavk@quicinc.com, bp@alien8.de, mchehab@kernel.org,
	linux-ext4@vger.kernel.org, tomba@kernel.org,
	hughlynch@google.com, sre@kernel.org, tfiga@chromium.org,
	linux-xfs@vger.kernel.org, zhangfei.gao@linaro.org,
	wangzhou1@hisilicon.com, netdev@vger.kernel.org,
	bpf@vger.kernel.org, linux-erofs@lists.ozlabs.org,
	davem@davemloft.net, mhocko@suse.com, kvm@vger.kernel.org,
	mst@redhat.com, peterz@infradead.org, bigeasy@linutronix.de,
	alexandre.torgue@foss.st.com, dhowells@redhat.com,
	linux-mm@kvack.org, ray.huang@amd.com, adilger.kernel@dilger.ca,
	kuba@kernel.org, sparclinux@vger.kernel.org, airlied@gmail.com,
	anton.ivanov@cambridgegreys.com, herbert@gondor.apana.org.au,
	linux-scsi@vger.kernel.org, richard@nod.at, x86@kernel.org,
	vkoul@kernel.org, mingo@redhat.com, axelrasmussen@google.com,
	intel-gfx@lists.freedesktop.org, daniel@ffwll.ch,
	paulmck@kernel.org, jannh@google.com, chao@kernel.org,
	maarten.lankhorst@linux.intel.com, liam.howlett@oracle.com,
	hdegoede@redhat.com, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, vbabka@suse.cz, dimitri.sivanich@hpe.com,
	amd-gfx@lists.freedesktop.org, posk@google.com,
	lstoakes@gmail.com, peterjung1337@gmail.com,
	yoshfuji@linux-ipv6.org, linuxppc-dev@lists.ozlabs.org,
	dsahern@kernel.org, kent.overstreet@linux.dev,
	kexec@lists.infradead.org, tiwai@suse.com,
	krzysztof.kozlowski@linaro.org, tzimmermann@suse.de,
	hannes@cmpxchg.org, dmitry.baryshkov@linaro.org,
	johannes@sipsolutions.net, mgorman@techsingularity.net,
	linux-accelerators@lists.ozlabs.org, l.stach@pengutronix.de
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, nvdimm@lists.linux.dev,
	leewalsh@google.com, dri-devel@lists.freedesktop.org,
	perex@perex.cz, jglisse@google.com, arjunroy@google.com,
	m.szyprowski@samsung.com, linux-arch@vger.kernel.org,
	qianweili@huawei.com, linux-samsung-soc@vger.kernel.org,
	aneesh.kumar@linux.ibm.com, chenhuacai@kernel.org,
	kasan-dev@googlegroups.com, linux-acpi@vger.kernel.org,
	rientjes@google.com, xen-devel@lists.xenproject.org,
	devel@lists.orangefs.org, minchan@google.com,
	robert.jarzmik@free.fr, linux-um@lists.infradead.org,
	etnaviv@lists.freedesktop.org, npiggin@gmail.com,
	alex.williamson@redhat.com, viro@zeniv.linux.org.uk,
	luto@kernel.org, gthelen@google.com, tglx@linutronix.de,
	ldufour@linux.ibm.com, surenb@google.com,
	linux-sgx@vger.kernel.org, martin.petersen@oracle.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-media@vger.kernel.org,
	freedreno@lists.freedesktop.org, joelaf@google.com,
	linux-aio@kvack.org, linux-fbdev@vger.kernel.org,
	linux-ia64@vger.kernel.org, david@redhat.com,
	dave.hansen@linux.intel.com,
	virtualization@lists.linux-foundation.org, edumazet@google.com,
	target-devel@vger.kernel.org, punit.agrawal@bytedance.com,
	linux-s390@vger.kernel.org, dave@stgolabs.net, deller@gmx.de,
	hughd@google.com, andrii@kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-rockchip@lists.infradead.org,
	linux-graphics-maintainer@vmware.com, kernel-team@android.com,
	jayalk@intworks.biz, soheil@google.com, selinux@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, shakeelb@google.com,
	haojian.zhuang@gmail.com, loongarch@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org, tytso@mit.edu,
	nico@fluxnic.net, muchun.song@linux.dev, hjc@rock-chips.com,
	mcoquelin.stm32@gmail.com, tatashin@google.com,
	mike.kravetz@oracle.com, songliubraving@fb.com,
	jasowang@redhat.com, alsa-devel@alsa-project.org,
	peterx@redhat.com, linux-tegra@vger.kernel.org,
	kraxel@redhat.com, will@kernel.org, dmaengine@vger.kernel.org,
	bhe@redhat.com, miklos@szeredi.hu, linux-rdma@vger.kernel.org,
	linux-staging@lists.linux.dev, willy@infradead.org,
	gurua@google.com, dgilbert@interlog.com, xiang@kernel.org,
	pabeni@redhat.com, jejb@linux.ibm.com, quic_abhinavk@quicinc.com,
	bp@alien8.de, mchehab@kernel.org, linux-ext4@vger.kernel.org,
	tomba@kernel.org, hughlynch@google.com, sre@kernel.org,
	tfiga@chromium.org, linux-xfs@vger.kernel.org,
	zhangfei.gao@linaro.org, wangzhou1@hisilicon.com,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-erofs@lists.ozlabs.org, davem@davemloft.net,
	mhocko@suse.com, kvm@vger.kernel.org, mst@redhat.com,
	peterz@infradead.org, bigeasy@linutronix.de,
	alexandre.torgue@foss.st.com, dhowells@redhat.com,
	linux-mm@kvack.org, ray.huang@amd.com, adilger.kernel@dilger.ca,
	kuba@kernel.org, sparclinux@vger.kernel.org,
	anton.ivanov@cambridgegreys.com, herbert@gondor.apana.org.au,
	linux-scsi@vger.kernel.org, richard@nod.at, x86@kernel.org,
	vkoul@kernel.org, mingo@redhat.com, axelrasmussen@google.com,
	intel-gfx@lists.freedesktop.org, paulmck@kernel.org,
	jannh@google.com, chao@kernel.org, liam.howlett@oracle.com,
	hdegoede@redhat.com, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, vbabka@suse.cz, dimitri.sivanich@hpe.com,
	amd-gfx@lists.freedesktop.org, posk@google.com,
	lstoakes@gmail.com, peterjung1337@gmail.com,
	yoshfuji@linux-ipv6.org, linuxppc-dev@lists.ozlabs.org,
	dsahern@kernel.org, kent.overstreet@linux.dev,
	kexec@lists.infradead.org, tiwai@suse.com,
	krzysztof.kozlowski@linaro.org, tzimmermann@suse.de,
	hannes@cmpxchg.org, dmitry.baryshkov@linaro.org,
	johannes@sipsolutions.net, mgorman@techsingularity.net,
	linux-accelerators@lists.ozlabs.org
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, nvdimm@lists.linux.dev, heiko@sntech.de,
	leewalsh@google.com, dri-devel@lists.freedesktop.org,
	jglisse@google.com, arjunroy@google.com,
	m.szyprowski@samsung.com, linux-arch@vger.kernel.org,
	qianweili@huawei.com, linux-samsung-soc@vger.kernel.org,
	aneesh.kumar@linux.ibm.com, chenhuacai@kernel.org,
	kasan-dev@googlegroups.com, linux-acpi@vger.kernel.org,
	rientjes@google.com, xen-devel@lists.xenproject.org,
	devel@lists.orangefs.org, robdclark@gmail.com,
	minchan@google.com, robert.jarzmik@free.fr,
	linux-um@lists.infradead.org, etnaviv@lists.freedesktop.org,
	npiggin@gmail.com, alex.williamson@redhat.com,
	viro@zeniv.linux.org.uk, luto@kernel.org, gthelen@google.com,
	tglx@linutronix.de, ldufour@linux.ibm.com, surenb@google.com,
	linux-sgx@vger.kernel.org, martin.petersen@oracle.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-media@vger.kernel.org,
	freedreno@lists.freedesktop.org, joelaf@google.com,
	linux-aio@kvack.org, linux-fbdev@vger.kernel.org,
	linux-ia64@vger.kernel.org, david@redhat.com,
	dave.hansen@linux.intel.com,
	virtualization@lists.linux-foundation.org, edumazet@google.com,
	target-devel@vger.kernel.org, punit.agrawal@bytedance.com,
	linux-s390@vger.kernel.org, dave@stgolabs.net, deller@gmx.de,
	hughd@google.com, andrii@kernel.org,
	patrik.r.jakobsson@gmail.com,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-rockchip@lists.infradead.org,
	linux-graphics-maintainer@vmware.com, kernel-team@android.com,
	jayalk@intworks.biz, soheil@google.com, selinux@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, mripard@kernel.org,
	shakeelb@google.com, haojian.zhuang@gmail.com,
	loongarch@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	tytso@mit.edu, nico@fluxnic.net, muchun.song@linux.dev,
	hjc@rock-chips.com, mcoquelin.stm32@gmail.com,
	tatashin@google.com, mike.kravetz@oracle.com,
	songliubraving@fb.com, jasowang@redhat.com,
	alsa-devel@alsa-project.org, peterx@redhat.com,
	linux-tegra@vger.kernel.org, kraxel@redhat.com, will@kernel.org,
	dmaengine@vger.kernel.org, bhe@redhat.com, miklos@szeredi.hu,
	linux-rdma@vger.kernel.org, linux-staging@lists.linux.dev,
	willy@infradead.org, gurua@google.com, dgilbert@interlog.com,
	xiang@kernel.org, pabeni@redhat.com, jejb@linux.ibm.com,
	quic_abhinavk@quicinc.com, bp@alien8.de, mchehab@kernel.org,
	linux-ext4@vger.kernel.org, tomba@kernel.org,
	hughlynch@google.com, sre@kernel.org, tfiga@chromium.org,
	linux-xfs@vger.kernel.org, zhangfei.gao@linaro.org,
	wangzhou1@hisilicon.com, netdev@vger.kernel.org,
	bpf@vger.kernel.org, linux-erofs@lists.ozlabs.org,
	davem@davemloft.net, mhocko@suse.com, kvm@vger.kernel.org,
	mst@redhat.com, peterz@infradead.org, bigeasy@linutronix.de,
	alexandre.torgue@foss.st.com, dhowells@redhat.com,
	linux-mm@kvack.org, ray.huang@amd.com, adilger.kernel@dilger.ca,
	kuba@kernel.org, sparclinux@vger.kernel.org, airlied@gmail.com,
	anton.ivanov@cambridgegreys.com, herbert@gondor.apana.org.au,
	linux-scsi@vger.kernel.org, richard@nod.at, x86@kernel.org,
	vkoul@kernel.org, mingo@redhat.com, axelrasmussen@google.com,
	intel-gfx@lists.freedesktop.org, daniel@ffwll.ch,
	paulmck@kernel.org, jannh@google.com, chao@kernel.org,
	maarten.lankhorst@linux.intel.com, liam.howlett@oracle.com,
	hdegoede@redhat.com, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, vbabka@suse.cz, dimitri.sivanich@hpe.com,
	amd-gfx@lists.freedesktop.org, posk@google.com,
	lstoakes@gmail.com, peterjung1337@gmail.com,
	yoshfuji@linux-ipv6.org, linuxppc-dev@lists.ozlabs.org,
	dsahern@kernel.org, kent.overstreet@linux.dev,
	kexec@lists.infradead.org, tiwai@suse.com,
	krzysztof.kozlowski@linaro.org, tzimmermann@suse.de,
	hannes@cmpxchg.org, dmitry.baryshkov@linaro.org,
	johannes@sipsolutions.net, mgorman@techsingularity.net,
	linux-accelerators@lists.ozlabs.org, l.stach@pengutronix.de
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, nvdimm@lists.linux.dev, heiko@sntech.de,
	leewalsh@google.com, dri-devel@lists.freedesktop.org,
	perex@perex.cz, jglisse@google.com, arjunroy@google.com,
	m.szyprowski@samsung.com, linux-arch@vger.kernel.org,
	qianweili@huawei.com, linux-samsung-soc@vger.kernel.org,
	aneesh.kumar@linux.ibm.com, chenhuacai@kernel.org,
	kasan-dev@googlegroups.com, linux-acpi@vger.kernel.org,
	rientjes@google.com, xen-devel@lists.xenproject.org,
	devel@lists.orangefs.org, robdclark@gmail.com,
	minchan@google.com, robert.jarzmik@free.fr,
	linux-um@lists.infradead.org, etnaviv@lists.freedesktop.org,
	npiggin@gmail.com, alex.williamson@redhat.com,
	viro@zeniv.linux.org.uk, luto@kernel.org, gthelen@google.com,
	tglx@linutronix.de, ldufour@linux.ibm.com, surenb@google.com,
	linux-sgx@vger.kernel.org, martin.petersen@oracle.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-media@vger.k ernel.org,
	freedreno@lists.freedesktop.org, joelaf@google.com,
	linux-aio@kvack.org, linux-fbdev@vger.kernel.org,
	linux-ia64@vger.kernel.org, david@redhat.com,
	dave.hansen@linux.intel.com,
	virtualization@lists.linux-foundation.org, edumazet@google.com,
	target-devel@vger.kernel.org, punit.agrawal@bytedance.com,
	linux-s390@vger.kernel.org, dave@stgolabs.net, deller@gmx.de,
	hughd@google.com, andrii@kernel.org,
	patrik.r.jakobsson@gmail.com,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-rockchip@lists.infradead.org,
	linux-graphics-maintainer@vmware.com, kernel-team@android.com,
	jayalk@intworks.biz, soheil@google.com, selinux@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, mripard@kernel.org,
	shakeelb@google.com, haojian.zhuang@gmail.com,
	loongarch@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	tytso@mit.edu, nico@fluxnic.net, muchun.song@linux.dev,
	hjc@rock-chips.com, mcoquelin.stm32@gmail.com,
	tatashin@google.com, mike.kravetz@oracle.com,
	songliubraving@fb.com, jasowang@redhat. com,
	alsa-devel@alsa-project.org, peterx@redhat.com,
	linux-tegra@vger.kernel.org, kraxel@redhat.com, will@kernel.org,
	dmaengine@vger.kernel.org, bhe@redhat.com, miklos@szeredi.hu,
	linux-rdma@vger.kernel.org, linux-staging@lists.linux.dev,
	willy@infradead.org, gurua@google.com, dgilbert@interlog.com,
	xiang@kernel.org, pabeni@redhat.com, jejb@linux.ibm.com,
	quic_abhinavk@quicinc.com, bp@alien8.de, mchehab@kernel.org,
	linux-ext4@vger.kernel.org, tomba@kernel.org,
	hughlynch@google.com, sre@kernel.org, tfiga@chromium.org,
	linux-xfs@vger.kernel.org, zhangfei.gao@linaro.org,
	wangzhou1@hisilicon.com, netdev@vger.kernel.org,
	bpf@vger.kernel.org, linux-erofs@lists.ozlabs.org,
	davem@davemloft.net, mhocko@suse.com, kvm@vger.kernel.org,
	mst@redhat.com, peterz@infradead.org, bigeasy@linutronix.de,
	alexandre.torgue@foss.st.com, dhowells@redhat.com,
	linux-mm@kvack.org, ray.huang@amd.com, adilger.kernel@dilger.ca,
	kuba@kernel.org, sparclinux@vger.kernel.org, airlied@gmail.com,
	anton.ivanov@cambridge greys.com, herbert@gondor.apana.org.au,
	linux-scsi@vger.kernel.org, richard@nod.at, x86@kernel.org,
	vkoul@kernel.org, mingo@redhat.com, axelrasmussen@google.com,
	intel-gfx@lists.freedesktop.org, daniel@ffwll.ch,
	paulmck@kernel.org, jannh@google.com, chao@kernel.org,
	maarten.lankhorst@linux.intel.com, liam.howlett@oracle.com,
	hdegoede@redhat.com, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, vbabka@suse.cz, dimitri.sivanich@hpe.com,
	amd-gfx@lists.freedesktop.org, posk@google.com,
	lstoakes@gmail.com, peterjung1337@gmail.com,
	yoshfuji@linux-ipv6.org, linuxppc-dev@lists.ozlabs.org,
	dsahern@kernel.org, kent.overstreet@linux.dev,
	kexec@lists.infradead.org, tiwai@suse.com,
	krzysztof.kozlowski@linaro.org, tzimmermann@suse.de,
	hannes@cmpxchg.org, dmitry.baryshkov@linaro.org,
	johannes@sipsolutions.net, mgorman@techsingularity.net,
	linux-accelerators@lists.ozlabs.org, l.stach@pengutronix.de
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, nvdimm@lists.linux.dev, heiko@sntech.de,
	leewalsh@google.com, dri-devel@lists.freedesktop.org,
	perex@perex.cz, jglisse@google.com, arjunroy@google.com,
	m.szyprowski@samsung.com, linux-arch@vger.kernel.org,
	qianweili@huawei.com, linux-samsung-soc@vger.kernel.org,
	aneesh.kumar@linux.ibm.com, chenhuacai@kernel.org,
	kasan-dev@googlegroups.com, linux-acpi@vger.kernel.org,
	rientjes@google.com, xen-devel@lists.xenproject.org,
	devel@lists.orangefs.org, minchan@google.com,
	robert.jarzmik@free.fr, linux-um@lists.infradead.org,
	etnaviv@lists.freedesktop.org, npiggin@gmail.com,
	viro@zeniv.linux.org.uk, luto@kernel.org, gthelen@google.com,
	tglx@linutronix.de, ldufour@linux.ibm.com, surenb@google.com,
	linux-sgx@vger.kernel.org, martin.petersen@oracle.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-media@vger.kernel.org,
	freedreno@lists.freedesktop.org, joelaf@google.com,
	linux-aio@kvack.org, linux-fbdev@vger.kernel.org,
	linux-ia64@vger.kernel.org, david@redhat.com,
	dave.hansen@linux.intel.com,
	virtualization@lists.linux-foundation.org, edumazet@google.com,
	target-devel@vger.kernel.org, punit.agrawal@bytedance.com,
	linux-s390@vger.kernel.org, dave@stgolabs.net, deller@gmx.de,
	hughd@google.com, andrii@kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-rockchip@lists.infradead.org,
	linux-graphics-maintainer@vmware.com, kernel-team@android.com,
	jayalk@intworks.biz, soheil@google.com, selinux@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, mripard@kernel.org,
	shakeelb@google.com, haojian.zhuang@gmail.com,
	loongarch@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	tytso@mit.edu, nico@fluxnic.net, muchun.song@linux.dev,
	hjc@rock-chips.com, mcoquelin.stm32@gmail.com,
	tatashin@google.com, mike.kravetz@oracle.com,
	songliubraving@fb.com, jasowang@redhat.com,
	alsa-devel@alsa-project.org, peterx@redhat.com,
	linux-tegra@vger.kernel.org, kraxel@redhat.com, will@kernel.org,
	dmaengine@vger.kernel.org, bhe@redhat.com, miklos@szeredi.hu,
	linux-rdma@vger.kernel.org, linux-staging@lists.linux.dev,
	willy@infradead.org, gurua@google.com, dgilbert@interlog.com,
	xiang@kernel.org, pabeni@redhat.com, jejb@linux.ibm.com,
	quic_abhinavk@quicinc.com, bp@alien8.de, mchehab@kernel.org,
	linux-ext4@vger.kernel.org, tomba@kernel.org,
	hughlynch@google.com, sre@kernel.org, tfiga@chromium.org,
	linux-xfs@vger.kernel.org, zhangfei.gao@linaro.org,
	wangzhou1@hisilicon.com, netdev@vger.kernel.org,
	bpf@vger.kernel.org, linux-erofs@lists.ozlabs.org,
	davem@davemloft.net, mhocko@suse.com, kvm@vger.kernel.org,
	mst@redhat.com, peterz@infradead.org, bigeasy@linutronix.de,
	alexandre.torgue@foss.st.com, dhowells@redhat.com,
	linux-mm@kvack.org, ray.huang@amd.com, adilger.kernel@dilger.ca,
	kuba@kernel.org, sparclinux@vger.kernel.org, airlied@gmail.com,
	anton.ivanov@cambridgegreys.com, herbert@gondor.apana.org.au,
	linux-scsi@vger.kernel.org, richard@nod.at, x86@kernel.org,
	vkoul@kernel.org, mingo@redhat.com, axelrasmussen@google.com,
	intel-gfx@lists.freedesktop.org, daniel@ffwll.ch,
	paulmck@kernel.org, jannh@google.com, chao@kernel.org,
	liam.howlett@oracle.com, hdegoede@redhat.com,
	linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com,
	vbabka@suse.cz, dimitri.sivanich@hpe.com,
	amd-gfx@lists.freedesktop.org, posk@google.com,
	lstoakes@gmail.com, peterjung1337@gmail.com,
	yoshfuji@linux-ipv6.org, linuxppc-dev@lists.ozlabs.org,
	dsahern@kernel.org, kent.overstreet@linux.dev,
	kexec@lists.infradead.org, tiwai@suse.com,
	krzysztof.kozlowski@linaro.org, tzimmermann@suse.de,
	hannes@cmpxchg.org, dmitry.baryshkov@linaro.org,
	johannes@sipsolutions.net, mgorman@techsingularity.net,
	linux-accelerators@lists.ozlabs.org, l.stach@pengutronix.de
Subject: [Intel-gfx] [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com,
	vbabka@suse.cz,  hannes@cmpxchg.org, mgorman@techsingularity.net,
	dave@stgolabs.net,  willy@infradead.org, liam.howlett@oracle.com,
	peterz@infradead.org,  ldufour@linux.ibm.com, paulmck@kernel.org,
	luto@kernel.org,  songliubraving@fb.com, peterx@redhat.com,
	david@redhat.com,  dhowells@redhat.com, hughd@google.com,
	bigeasy@linutronix.de,  kent.overstreet@linux.dev,
	punit.agrawal@bytedance.com, lstoakes@gmail.com,
	 peterjung1337@gmail.com, rientjes@google.com,
	axelrasmussen@google.com,  joelaf@google.com, minchan@google.com,
	jannh@google.com, shakeelb@google.com,  tatashin@google.com,
	edumazet@google.com, gthelen@google.com,  gurua@google.com,
	arjunroy@google.com, soheil@google.com,  hughlynch@google.com,
	leewalsh@google.com, posk@google.com, will@kernel.org,
	 aneesh.kumar@linux.ibm.com, npiggin@gmail.com,
	chenhuacai@kernel.org,  tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de,  dave.hansen@linux.intel.com, richard@nod.at,
	anton.ivanov@cambridgegreys.com,  johannes@sipsolutions.net,
	qianweili@huawei.com, wangzhou1@hisilicon.com,
	 herbert@gondor.apana.org.au, davem@davemloft.net,
	vkoul@kernel.org,  airlied@gmail.com, daniel@ffwll.ch,
	maarten.lankhorst@linux.intel.com,  mripard@kernel.org,
	tzimmermann@suse.de, l.stach@pengutronix.de,
	 krzysztof.kozlowski@linaro.org, patrik.r.jakobsson@gmail.com,
	 matthias.bgg@gmail.com, robdclark@gmail.com,
	quic_abhinavk@quicinc.com,  dmitry.baryshkov@linaro.org,
	tomba@kernel.org, hjc@rock-chips.com,  heiko@sntech.de,
	ray.huang@amd.com, kraxel@redhat.com, sre@kernel.org,
	 mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
	tfiga@chromium.org,  m.szyprowski@samsung.com,
	mchehab@kernel.org, dimitri.sivanich@hpe.com,
	 zhangfei.gao@linaro.org, jejb@linux.ibm.com,
	martin.petersen@oracle.com,  dgilbert@interlog.com,
	hdegoede@redhat.com, mst@redhat.com,  jasowang@redhat.com,
	alex.williamson@redhat.com, deller@gmx.de,  jayalk@intworks.biz,
	viro@zeniv.linux.org.uk, nico@fluxnic.net,  xiang@kernel.org,
	chao@kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
	 miklos@szeredi.hu, mike.kravetz@oracle.com,
	muchun.song@linux.dev,  bhe@redhat.com, andrii@kernel.org,
	yoshfuji@linux-ipv6.org,  dsahern@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, perex@perex.cz,  tiwai@suse.com,
	haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
	 linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	 linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	 linux-graphics-maintainer@vmware.com,
	linux-ia64@vger.kernel.org,  linux-arch@vger.kernel.org,
	loongarch@lists.linux.dev, kvm@vger.kernel.org,
	 linux-s390@vger.kernel.org, linux-sgx@vger.kernel.org,
	 linux-um@lists.infradead.org, linux-acpi@vger.kernel.org,
	 linux-crypto@vger.kernel.org, nvdimm@lists.linux.dev,
	 dmaengine@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	 dri-devel@lists.freedesktop.org, etnaviv@lists.freedesktop.org,
	 linux-samsung-soc@vger.kernel.org,
	intel-gfx@lists.freedesktop.org,
	 linux-mediatek@lists.infradead.org,
	linux-arm-msm@vger.kernel.org,  freedreno@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org,  linux-tegra@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	 xen-devel@lists.xenproject.org,
	linux-stm32@st-md-mailman.stormreply.com,
	 linux-rdma@vger.kernel.org, linux-media@vger.kernel.org,
	 linux-accelerators@lists.ozlabs.org, sparclinux@vger.kernel.org,
	 linux-scsi@vger.kernel.org, linux-staging@lists.linux.dev,
	 target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
	 netdev@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-aio@kvack.org,  linux-fsdevel@vger.kernel.org,
	linux-erofs@lists.ozlabs.org,  linux-ext4@vger.kernel.org,
	devel@lists.orangefs.org,  kexec@lists.infradead.org,
	linux-xfs@vger.kernel.org, bpf@vger.kernel.org,
	 linux-perf-users@vger.kernel.org, kasan-dev@googlegroups.com,
	 selinux@vger.kernel.org, alsa-devel@alsa-project.org,
	kernel-team@android.com,  surenb@google.com
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 00:38:46 -0800	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com,
	vbabka@suse.cz, hannes@cmpxchg.org, mgorman@techsingularity.net,
	dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com,
	peterz@infradead.org, ldufour@linux.ibm.com, paulmck@kernel.org,
	luto@kernel.org, songliubraving@fb.com, peterx@redhat.com,
	david@redhat.com, dhowells@redhat.com, hughd@google.com,
	bigeasy@linutronix.de, kent.overstreet@linux.dev,
	punit.agrawal@bytedance.com, lstoakes@gmail.com,
	peterjung1337@gmail.com, rientjes@google.com,
	axelrasmussen@google.com, joelaf@google.com, minchan@google.com,
	jannh@google.com, shakeelb@google.com, tatashin@google.com,
	edumazet@google.com, gthelen@google.com, gurua@google.com,
	arjunroy@google.com, soheil@google.com, hughlynch@google.com,
	leewalsh@google.com, posk@google.com, will@kernel.org,
	aneesh.kumar@linux.ibm.com, npiggin@gmail.com,
	chenhuacai@kernel.org, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, richard@nod.at,
	anton.ivanov@cambridgegreys.com, johannes@sipsolutions.net,
	qianweili@huawei.com, wangzhou1@hisilicon.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	vkoul@kernel.org, airlied@gmail.com, daniel@ffwll.ch,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, l.stach@pengutronix.de,
	krzysztof.kozlowski@linaro.org, patrik.r.jakobsson@gmail.com,
	matthias.bgg@gmail.com, robdclark@gmail.com,
	quic_abhinavk@quicinc.com, dmitry.baryshkov@linaro.org,
	tomba@kernel.org, hjc@rock-chips.com, heiko@sntech.de,
	ray.huang@amd.com, kraxel@redhat.com, sre@kernel.org,
	mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
	tfiga@chromium.org, m.szyprowski@samsung.com, mchehab@kernel.org,
	dimitri.sivanich@hpe.com, zhangfei.gao@linaro.org,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	dgilbert@interlog.com, hdegoede@redhat.com, mst@redhat.com,
	jasowang@redhat.com, alex.williamson@redhat.com, deller@gmx.de,
	jayalk@intworks.biz, viro@zeniv.linux.org.uk, nico@fluxnic.net,
	xiang@kernel.org, chao@kernel.org, tytso@mit.edu,
	adilger.kernel@dilger.ca, miklos@szeredi.hu,
	mike.kravetz@oracle.com, muchun.song@linux.dev, bhe@redhat.com,
	andrii@kernel.org, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, perex@perex.cz,
	tiwai@suse.com, haojian.zhuang@gmail.com, robert.jarzmik@free.fr,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-graphics-maintainer@vmware.com, linux-ia64@vger.kernel.org,
	linux-arch@vger.kernel.org, loongarch@lists.linux.dev,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-sgx@vger.kernel.org, linux-um@lists.infradead.org,
	linux-acpi@vger.kernel.org, linux-crypto@vger.kernel.org,
	nvdimm@lists.linux.dev, dmaengine@vger.kernel.org,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	etnaviv@lists.freedesktop.org, linux-samsung-soc@vger.kernel.org,
	intel-gfx@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org, linux-tegra@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xenproject.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-rdma@vger.kernel.org, linux-media@vger.kernel.org,
	linux-accelerators@lists.ozlabs.org, sparclinux@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-staging@lists.linux.dev,
	target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
	netdev@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-aio@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-erofs@lists.ozlabs.org, linux-ext4@vger.kernel.org,
	devel@lists.orangefs.org, kexec@lists.infradead.org,
	linux-xfs@vger.kernel.org, bpf@vger.kernel.org,
	linux-perf-users@vger.kernel.org, kasan-dev@googlegroups.com,
	selinux@vger.kernel.org, alsa-devel@alsa-project.org,
	kernel-team@android.com, surenb@google.com
Subject: [PATCH v2 1/6] mm: introduce vma->vm_flags modifier functions
Date: Wed, 25 Jan 2023 08:38:46 +0000	[thread overview]
Message-ID: <20230125083851.27759-2-surenb@google.com> (raw)
In-Reply-To: <20230125083851.27759-1-surenb@google.com>

vm_flags are among VMA attributes which affect decisions like VMA merging
and splitting. Therefore all vm_flags modifications are performed after
taking exclusive mmap_lock to prevent vm_flags updates racing with such
operations. Introduce modifier functions for vm_flags to be used whenever
flags are updated. This way we can better check and control correct
locking behavior during these updates.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 include/linux/mm.h       | 37 +++++++++++++++++++++++++++++++++++++
 include/linux/mm_types.h |  8 +++++++-
 2 files changed, 44 insertions(+), 1 deletion(-)

diff --git a/include/linux/mm.h b/include/linux/mm.h
index c2f62bdce134..b71f2809caac 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -627,6 +627,43 @@ static inline void vma_init(struct vm_area_struct *vma, struct mm_struct *mm)
 	INIT_LIST_HEAD(&vma->anon_vma_chain);
 }
 
+/* Use when VMA is not part of the VMA tree and needs no locking */
+static inline void init_vm_flags(struct vm_area_struct *vma,
+				 unsigned long flags)
+{
+	vma->vm_flags = flags;
+}
+
+/* Use when VMA is part of the VMA tree and modifications need coordination */
+static inline void reset_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	init_vm_flags(vma, flags);
+}
+
+static inline void set_vm_flags(struct vm_area_struct *vma,
+				unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= flags;
+}
+
+static inline void clear_vm_flags(struct vm_area_struct *vma,
+				  unsigned long flags)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags &= ~flags;
+}
+
+static inline void mod_vm_flags(struct vm_area_struct *vma,
+				unsigned long set, unsigned long clear)
+{
+	mmap_assert_write_locked(vma->vm_mm);
+	vma->vm_flags |= set;
+	vma->vm_flags &= ~clear;
+}
+
 static inline void vma_set_anonymous(struct vm_area_struct *vma)
 {
 	vma->vm_ops = NULL;
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 2d6d790d9bed..6c7c70bf50dd 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -491,7 +491,13 @@ struct vm_area_struct {
 	 * See vmf_insert_mixed_prot() for discussion.
 	 */
 	pgprot_t vm_page_prot;
-	unsigned long vm_flags;		/* Flags, see mm.h. */
+
+	/*
+	 * Flags, see mm.h.
+	 * WARNING! Do not modify directly.
+	 * Use {init|reset|set|clear|mod}_vm_flags() functions instead.
+	 */
+	unsigned long vm_flags;
 
 	/*
 	 * For areas with an address space and backing store,
-- 
2.39.1

  reply	other threads:[~2023-01-25  8:38 UTC|newest]

Thread overview: 314+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  8:38 [PATCH v2 0/6] introduce vm_flags modifier functions Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan
2023-01-25  8:38 ` Suren Baghdasaryan [this message]
2023-01-25  8:38   ` [PATCH v2 1/6] mm: introduce vma->vm_flags " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:56   ` Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  8:56     ` [Intel-gfx] " Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  8:56     ` Michal Hocko
2023-01-25  9:09   ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` [Intel-gfx] " Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25  9:09     ` Peter Zijlstra
2023-01-25 16:49     ` Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 16:49       ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 16:49       ` Suren Baghdasaryan
2023-01-25 18:37       ` Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 18:37         ` [Intel-gfx] " Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 18:37         ` Matthew Wilcox
2023-01-25 19:21         ` Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 19:21           ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 19:21           ` Suren Baghdasaryan
2023-01-25 20:35           ` Matthew Wilcox
2023-01-25 21:04             ` Suren Baghdasaryan
2023-01-25 21:07               ` Suren Baghdasaryan
2023-01-25 21:08                 ` Suren Baghdasaryan
2023-01-25 22:02                   ` Matthew Wilcox
2023-01-25 22:15             ` Suren Baghdasaryan
2023-01-25 18:33   ` Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 18:33     ` [Intel-gfx] " Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 18:33     ` Matthew Wilcox
2023-01-25 19:22     ` Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-25 19:22       ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-25 19:22       ` Suren Baghdasaryan
2023-01-26  9:17   ` Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26  9:17     ` [Intel-gfx] " Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26  9:17     ` Mike Rapoport
2023-01-26 14:50     ` Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 14:50       ` [Intel-gfx] " Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 14:50       ` Mike Rapoport
2023-01-26 15:09       ` Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 15:09         ` [Intel-gfx] " Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 15:09         ` Matthew Wilcox
2023-01-26 16:25         ` Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-26 16:25           ` [Intel-gfx] " Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-26 16:25           ` Suren Baghdasaryan
2023-01-25  8:38 ` [PATCH v2 2/6] mm: replace VM_LOCKED_CLEAR_MASK with VM_LOCKED_MASK Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  9:02   ` Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-25  9:02     ` [Intel-gfx] " Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-25  9:02     ` Michal Hocko
2023-01-26  9:19   ` Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-26  9:19     ` [Intel-gfx] " Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-26  9:19     ` Mike Rapoport
2023-01-25  8:38 ` [PATCH v2 3/6] mm: replace vma->vm_flags direct modifications with modifier calls Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  9:30   ` Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25  9:30     ` [Intel-gfx] " Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25  9:30     ` Michal Hocko
2023-01-25 16:55     ` Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-25 16:55       ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-25 16:55       ` Suren Baghdasaryan
2023-01-26  9:21   ` Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26  9:21     ` [Intel-gfx] " Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26  9:21     ` Mike Rapoport
2023-01-26 17:07   ` Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-26 17:07     ` [Intel-gfx] " Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-26 17:07     ` Sebastian Reichel
2023-01-25  8:38 ` [PATCH v2 4/6] mm: replace vma->vm_flags indirect modification in ksm_madvise Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  9:38   ` Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25  9:38     ` [Intel-gfx] " Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25  9:38     ` Michal Hocko
2023-01-25 16:57     ` Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 16:57       ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 16:57       ` Suren Baghdasaryan
2023-01-25 17:08       ` Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:08         ` [Intel-gfx] " Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:08         ` Michal Hocko
2023-01-25 17:22         ` Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-25 17:22           ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-25 17:22           ` Suren Baghdasaryan
2023-01-26  9:26   ` Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-26  9:26     ` [Intel-gfx] " Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-26  9:26     ` Mike Rapoport
2023-01-25  8:38 ` [PATCH v2 5/6] mm: introduce mod_vm_flags_nolock and use it in untrack_pfn Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  9:42   ` Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25  9:42     ` [Intel-gfx] " Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25  9:42     ` Michal Hocko
2023-01-25 16:59     ` Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-25 17:00       ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-25 17:00       ` Suren Baghdasaryan
2023-01-26  9:34   ` Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-26  9:34     ` [Intel-gfx] " Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-26  9:34     ` Mike Rapoport
2023-01-25  8:38 ` [PATCH v2 6/6] mm: export dump_mm() Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` [Intel-gfx] " Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  8:38   ` Suren Baghdasaryan
2023-01-25  9:43   ` Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-25  9:43     ` [Intel-gfx] " Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-25  9:43     ` Michal Hocko
2023-01-26 14:48   ` Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-01-26 14:48     ` [Intel-gfx] " Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-01-26 14:48     ` Mike Rapoport
2023-02-02 16:21 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for introduce vm_flags modifier functions Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230125083851.27759-2-surenb@google.com \
    --to=surenb@google.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andrii@kernel.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=arjunroy@google.com \
    --cc=axelrasmussen@google.com \
    --cc=bhe@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=bpf@vger.kernel.org \
    --cc=chao@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@stgolabs.net \
    --cc=davem@davemloft.net \
    --cc=david@redhat.com \
    --cc=deller@gmx.de \
    --cc=devel@lists.orangefs.org \
    --cc=dgilbert@interlog.com \
    --cc=dhowells@redhat.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=gthelen@google.com \
    --cc=gurua@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=heiko@sntech.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=hjc@rock-chips.com \
    --cc=hughd@google.com \
    --cc=hughlynch@google.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jannh@google.com \
    --cc=jasowang@redhat.com \
    --cc=jayalk@intworks.biz \
    --cc=jejb@linux.ibm.com \
    --cc=jglisse@google.com \
    --cc=joelaf@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kasan-dev@googlegroups.com \
    --cc=kent.overstreet@linux.dev \
    --cc=kernel-team@android.com \
    --cc=kexec@lists.infradead.org \
    --cc=kraxel@redhat.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=ldufour@linux.ibm.com \
    --cc=leewalsh@google.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-accelerators@lists.ozlabs.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-aio@kvack.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=lstoakes@gmail.com \
    --cc=luto@kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=michel@lespinasse.org \
    --cc=mike.kravetz@oracle.com \
    --cc=miklos@szeredi.hu \
    --cc=minchan@google.com \
    --cc=mingo@redhat.com \
    --cc=mripard@kernel.org \
    --cc=mst@redhat.com \
    --cc=muchun.song@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=npiggin@gmail.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=patrik.r.jakobsson@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=perex@perex.cz \
    --cc=peterjung1337@gmail.com \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=posk@google.com \
    --cc=punit.agrawal@bytedance.com \
    --cc=qianweili@huawei.com \
    --cc=quic_abhinavk@quicinc.com \
    --cc=ray.huang@amd.com \
    --cc=richard@nod.at \
    --cc=rientjes@google.com \
    --cc=robdclark@gmail.com \
    --cc=robert.jarzmik@free.fr \
    --cc=selinux@vger.kernel.org \
    --cc=shakeelb@google.com \
    --cc=soheil@google.com \
    --cc=songliubraving@fb.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=target-devel@vger.kernel.org \
    --cc=tatashin@google.com \
    --cc=tfiga@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.com \
    --cc=tomba@kernel.org \
    --cc=tytso@mit.edu \
    --cc=tzimmermann@suse.de \
    --cc=vbabka@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=vkoul@kernel.org \
    --cc=wangzhou1@hisilicon.com \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xiang@kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    --cc=zhangfei.gao@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.