Linux Kernel Selftest development
 help / color / mirror / Atom feed
* make run_tests -C proc: proc-pid-vm assertion failed.
@ 2022-09-09  2:19 Jie2x Zhou
  2022-09-09  5:20 ` Alexey Dobriyan
  0 siblings, 1 reply; 3+ messages in thread
From: Jie2x Zhou @ 2022-09-09  2:19 UTC (permalink / raw)
  To: jie2x.zhou, shuah, adobriyan, guozhengkui
  Cc: akpm, linux-kernel, linux-fsdevel, linux-kselftest, Philip Li

hi,

The test error is caused by g_vsyscall set failed.

Error output:
 selftests: proc: proc-pid-vm
 proc-pid-vm: proc-pid-vm.c:389: main: Assertion `rv == len' failed.
 Aborted

g_vsyscall is set to 0.
In proc-pid-vm.c:
/*
 * 0: vsyscall VMA doesn't exist        vsyscall=none
 * 1: vsyscall VMA is r-xp              vsyscall=emulate
 * 2: vsyscall VMA is --xp              vsyscall=xonly
 */
static int g_vsyscall;
static const char *str_vsyscall;

static const char str_vsyscall_0[] = "";
static const char str_vsyscall_1[] =
"ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]\n";
static const char str_vsyscall_2[] =
"ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0                  [vsyscall]\n";

The /proc/%u/maps output is:
buf=100000000-100001000 r-xp 00000000 00:2d 2                                /tmp/#2 (deleted)
ffffffffff600000-ffffffffff601000 --xp 00000000 00:00 0                  [vsyscall]

So the g_vsyscall should be 2 according to commentary(2: vsyscall VMA is --xp).
Is it a bug?

best regards,

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-09-13  5:13 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-09-09  2:19 make run_tests -C proc: proc-pid-vm assertion failed Jie2x Zhou
2022-09-09  5:20 ` Alexey Dobriyan
2022-09-13  5:13   ` Zhou, Jie2X

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox