From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,surenb@google.com,shuah@kernel.org,
reddybalavignesh9979@gmail.com,liam@infradead.org,kmehltretter@gmail.com,
joe@perches.com,apw@canonical.com,fuqingshuang@kylinos.cn,
akpm@linux-foundation.org
Subject: + selftests-proc-include-linux-mmanh-for-mremap_dontunmap.patch added to mm-new branch
Date: Thu, 19 Nov 2026 19:24:18 -0800 [thread overview]
Message-ID: <20261120032418.CB6E01F000CA@smtp.kernel.org> (raw)
In-Reply-To: <20261120022710.1585112-1-fuqingshuang@kylinos.cn>
The patch titled
Subject: selftests/proc: include linux/mman.h for MREMAP_DONTUNMAP
has been added to the -mm mm-new branch. Its filename is
selftests-proc-include-linux-mmanh-for-mremap_dontunmap.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/selftests-proc-include-linux-mmanh-for-mremap_dontunmap.patch
This patch will later appear in the mm-new branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Note, mm-new is a provisional staging ground for work-in-progress
patches, and acceptance into mm-new is a notification for others take
notice and to finish up reviews. Please do not hesitate to respond to
review feedback and post updated versions to replace or incrementally
fixup patches in mm-new.
The mm-new branch of mm.git is not included in linux-next
If a few days of testing in mm-new is successful, the patch will me moved
into mm.git's mm-unstable branch, which is included in linux-next
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Qingshuang Fu <fuqingshuang@kylinos.cn>
Subject: selftests/proc: include linux/mman.h for MREMAP_DONTUNMAP
Date: Fri, 20 Nov 2026 10:27:10 +0800
glibc versions before 2.32 do not define MREMAP_DONTUNMAP in <sys/mman.h>,
so proc-maps-race fails to build against them (e.g. glibc 2.31):
$ make -C tools/testing/selftests TARGETS=proc
...
proc-maps-race.c:691:58: error: 'MREMAP_DONTUNMAP' undeclared
(first use in this function)
Include <linux/mman.h> to get the flag from the kernel UAPI headers
instead of depending on the libc version. The proc Makefile already adds
those headers to the include path via $(TOOLS_INCLUDES).
Link: https://patch.msgid.link/20261120022710.1585112-1-fuqingshuang@kylinos.cn
Fixes: 6a45336b9b6f ("selftests/proc: extend /proc/pid/maps tearing test to include vma remapping")
Signed-off-by: Qingshuang Fu <fuqingshuang@kylinos.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Whitcroft <apw@canonical.com>
Cc: Joe Perches <joe@perches.com>
Cc: Shuah Khan <shuah@kernel.org>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Liam R. Howlett <liam@infradead.org>
Cc: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>
tools/testing/selftests/proc/proc-maps-race.c | 1 +
1 file changed, 1 insertion(+)
--- a/tools/testing/selftests/proc/proc-maps-race.c~selftests-proc-include-linux-mmanh-for-mremap_dontunmap
+++ a/tools/testing/selftests/proc/proc-maps-race.c
@@ -33,6 +33,7 @@
#include <string.h>
#include <unistd.h>
#include <linux/fs.h>
+#include <linux/mman.h>
#include <sys/ioctl.h>
#include <sys/mman.h>
#include <sys/stat.h>
_
Patches currently in -mm which might be from fuqingshuang@kylinos.cn are
selftests-proc-include-linux-mmanh-for-mremap_dontunmap.patch
prev parent reply other threads:[~2026-11-20 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 2:27 [PATCH] selftests/proc: include linux/mman.h for MREMAP_DONTUNMAP Qingshuang Fu
2026-11-20 3:24 ` Andrew Morton
2026-11-20 3:24 ` Andrew Morton [this message]
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=20261120032418.CB6E01F000CA@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=fuqingshuang@kylinos.cn \
--cc=joe@perches.com \
--cc=kmehltretter@gmail.com \
--cc=liam@infradead.org \
--cc=mm-commits@vger.kernel.org \
--cc=reddybalavignesh9979@gmail.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
/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.