All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, shuah@kernel.org,
	adobriyan@gmail.com, punit.agrawal@bytedance.com,
	akpm@linux-foundation.org
Subject: [nacked] selftests-proc-mark-proc-pid-vm-as-x86_64-only.patch removed from -mm tree
Date: Wed, 09 Nov 2022 19:23:10 -0800	[thread overview]
Message-ID: <20221110032311.AB5F6C433D6@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: selftests: proc: mark proc-pid-vm as x86_64 only
has been removed from the -mm tree.  Its filename was
     selftests-proc-mark-proc-pid-vm-as-x86_64-only.patch

This patch was dropped because it was nacked

------------------------------------------------------
From: Punit Agrawal <punit.agrawal@bytedance.com>
Subject: selftests: proc: mark proc-pid-vm as x86_64 only
Date: Wed, 9 Nov 2022 22:11:04 +0000

The proc-pid-vm test does not have support for architectures other than
x86_64.  Mark it as such in the Makefile and in the process remove the
special casing in the test itself.

Link: https://lkml.kernel.org/r/20221109221104.1797802-2-punit.agrawal@bytedance.com
Signed-off-by: Punit Agrawal <punit.agrawal@bytedance.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 tools/testing/selftests/proc/Makefile      |    2 +-
 tools/testing/selftests/proc/proc-pid-vm.c |    9 ---------
 2 files changed, 1 insertion(+), 10 deletions(-)

--- a/tools/testing/selftests/proc/Makefile~selftests-proc-mark-proc-pid-vm-as-x86_64-only
+++ a/tools/testing/selftests/proc/Makefile
@@ -11,7 +11,6 @@ TEST_GEN_PROGS += fd-001-lookup
 TEST_GEN_PROGS += fd-002-posix-eq
 TEST_GEN_PROGS += fd-003-kthread
 TEST_GEN_PROGS += proc-loadavg-001
-TEST_GEN_PROGS += proc-pid-vm
 TEST_GEN_PROGS += proc-self-map-files-001
 TEST_GEN_PROGS += proc-self-map-files-002
 TEST_GEN_PROGS += proc-self-syscall
@@ -29,6 +28,7 @@ TEST_GEN_PROGS += proc-multiple-procfs
 TEST_GEN_PROGS += proc-fsconfig-hidepid
 
 TEST_GEN_PROGS_x86_64 += proc-empty-vm
+TEST_GEN_PROGS_x86_64 += proc-pid-vm
 
 TEST_GEN_PROGS += $(TEST_GEN_PROGS_$(ARCH))
 
--- a/tools/testing/selftests/proc/proc-pid-vm.c~selftests-proc-mark-proc-pid-vm-as-x86_64-only
+++ a/tools/testing/selftests/proc/proc-pid-vm.c
@@ -105,7 +105,6 @@ struct elf64_phdr {
 	uint64_t p_align;
 };
 
-#ifdef __x86_64__
 #define PAGE_SIZE 4096
 #define VADDR (1UL << 32)
 #define MAPS_OFFSET 73
@@ -209,7 +208,6 @@ static int make_exe(const uint8_t *paylo
 
 	return fd1;
 }
-#endif
 
 /*
  * 0: vsyscall VMA doesn't exist	vsyscall=none
@@ -225,7 +223,6 @@ static const char str_vsyscall_1[] =
 static const char str_vsyscall_2[] =
 "ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]\n";
 
-#ifdef __x86_64__
 static void sigaction_SIGSEGV(int _, siginfo_t *__, void *___)
 {
 	_exit(g_vsyscall);
@@ -493,9 +490,3 @@ int main(void)
 
 	return 0;
 }
-#else
-int main(void)
-{
-	return 4;
-}
-#endif
_

Patches currently in -mm which might be from punit.agrawal@bytedance.com are



                 reply	other threads:[~2022-11-10  3:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221110032311.AB5F6C433D6@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=punit.agrawal@bytedance.com \
    --cc=shuah@kernel.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.