From: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
To: linux-kselftest@vger.kernel.org
Cc: Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Brian Foster <bfoster@redhat.com>,
Guo Zhengkui <guozhengkui@vivo.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: BUG: core dump in selftest of proc fs
Date: Wed, 4 Jan 2023 19:27:40 +0100 [thread overview]
Message-ID: <fd9206f6-3ec4-cafc-e313-dfddf957bd5e@alu.unizg.hr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Dear all,
Trying to complete `make kselftest` for the first time, so maybe I'm doing something wrong?
Or we are having a regression in 6.2-rc2 release candidate ...
However, the output of selftest run is:
make[2]: Entering directory '.../linux_torvalds/tools/testing/selftests/proc'
TAP version 13
1..21
# selftests: proc: fd-001-lookup
ok 1 selftests: proc: fd-001-lookup
# selftests: proc: fd-002-posix-eq
ok 2 selftests: proc: fd-002-posix-eq
# selftests: proc: fd-003-kthread
ok 3 selftests: proc: fd-003-kthread
# selftests: proc: proc-loadavg-001
ok 4 selftests: proc: proc-loadavg-001
# selftests: proc: proc-empty-vm
# proc-empty-vm: proc-empty-vm.c:184: test_proc_pid_maps: Assertion `rv == 0' failed.
# /usr/bin/timeout: the monitored command dumped core
# Aborted
not ok 5 selftests: proc: proc-empty-vm # exit=134
# selftests: proc: proc-pid-vm
# proc-pid-vm: proc-pid-vm.c:365: main: Assertion `rv == len' failed.
# /usr/bin/timeout: the monitored command dumped core
# Aborted
Please find attached lshw output, dmesg, config and lsmod.
I am available for further diagnostics.
The platform is Ubuntu 22.10 kinetic kudu on a Lenovo Ideapad 3 15ITL6 laptop.
Kind regards,
Mirsad
--
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu
--
System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
The European Union
[-- Attachment #2: config-6.2.0-rc2-mglru-kmemlk-nokasan+.xz --]
[-- Type: application/x-xz, Size: 44904 bytes --]
[-- Attachment #3: dmesg.log.xz --]
[-- Type: application/x-xz, Size: 26936 bytes --]
[-- Attachment #4: lshw.txt.xz --]
[-- Type: application/x-xz, Size: 5184 bytes --]
[-- Attachment #5: lsmod.txt.xz --]
[-- Type: application/x-xz, Size: 3412 bytes --]
next reply other threads:[~2023-01-04 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 18:27 Mirsad Goran Todorovac [this message]
2023-01-04 18:36 ` BUG: core dump in selftest of proc fs Alexey Dobriyan
2023-01-06 13:49 ` Mirsad Goran Todorovac
2023-01-06 10:39 ` Alexey Dobriyan
2023-01-06 13:53 ` Mirsad Goran Todorovac
2023-01-06 19:30 ` [PATCH] proc: fix PIE proc-empty-vm, proc-pid-vm tests Alexey Dobriyan
2023-01-06 20:53 ` Mirsad Goran Todorovac
2023-01-06 21:18 ` BUG: assert spuriously fails in selftest/proc/proc-uptime-001.c Mirsad Goran Todorovac
2023-01-06 22:06 ` Mirsad Goran Todorovac
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=fd9206f6-3ec4-cafc-e313-dfddf957bd5e@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfoster@redhat.com \
--cc=guozhengkui@vivo.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).