From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Yifei Liu <yifei.l.liu@oracle.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH Linux-6.12.y 1/1] selftests/mm: build with -O2
Date: Tue, 4 Feb 2025 11:34:09 -0500 [thread overview]
Message-ID: <20250204112244-142a14969c83de4a@stable.kernel.org> (raw)
In-Reply-To: <20250203233342.51041-1-yifei.l.liu@oracle.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 46036188ea1f5266df23a6149dea0df1c77cd1c7
WARNING: Author mismatch between patch and upstream commit:
Backport author: Yifei Liu<yifei.l.liu@oracle.com>
Commit author: Kevin Brodsky<kevin.brodsky@arm.com>
Status in newer kernel trees:
6.13.y | Not found
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: 46036188ea1f5 ! 1: e96302cf58b1e selftests/mm: build with -O2
@@ Metadata
## Commit message ##
selftests/mm: build with -O2
+ [ Upstream commit 46036188ea1f5266df23a6149dea0df1c77cd1c7 ]
+
The mm kselftests are currently built with no optimisation (-O0). It's
unclear why, and besides being obviously suboptimal, this also prevents
the pkeys tests from working as intended. Let's build all the tests with
@@ Commit message
Cc: Ryan Roberts <ryan.roberts@arm.com>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+ (cherry picked from commit 46036188ea1f5266df23a6149dea0df1c77cd1c7)
+ [Yifei: This commit also fix the failure of pkey_sighandler_tests_64,
+ which is also in linux-6.12.y, thus backport this commit]
+ Signed-off-by: Yifei Liu <yifei.l.liu@oracle.com>
## tools/testing/selftests/mm/Makefile ##
@@ tools/testing/selftests/mm/Makefile: endif
@@ tools/testing/selftests/mm/Makefile: endif
+# warnings.
+CFLAGS += -U_FORTIFY_SOURCE
+
- KDIR ?= /lib/modules/$(shell uname -r)/build
- ifneq (,$(wildcard $(KDIR)/Module.symvers))
- ifneq (,$(wildcard $(KDIR)/include/linux/page_frag_cache.h))
+ TEST_GEN_FILES = cow
+ TEST_GEN_FILES += compaction_test
+ TEST_GEN_FILES += gup_longterm
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
prev parent reply other threads:[~2025-02-04 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 23:33 [PATCH Linux-6.12.y 1/1] selftests/mm: build with -O2 Yifei Liu
2025-02-04 13:55 ` Greg KH
2025-02-04 16:34 ` Sasha Levin [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=20250204112244-142a14969c83de4a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yifei.l.liu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox