linux-kernel - Re: PROBLEM: found 2 tests failed using "perf test" command

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 22 May 2018 15:47:57 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
Cc:     peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
        alexander.shishkin@...ux.intel.com, namhyung@...nel.org,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: found 2 tests failed using "perf test" command

On Sun, May 20, 2018 at 01:53:15AM +0530, Jeffrin Thalakkottoor wrote:
> hello,
> 
> 
> i found two tests failed while i did "sudo ./perf test"
> 
> --------------------------------------------------------------------------->
> 24: Object code reading                                   : FAILED!
> 64: probe libc's inet_pton & backtrace it with ping       : FAILED!
> ---------------------------------------------------------------------------->
> 
> some relevent shell session details from ./sudo perf test -vv 24
> -------------------------------------------------------------------------------------------------------->
> Objdump command is: objdump -z -d --start-address=0xffffffff8132dda7
> --stop-address=0xffffffff8132de27
> /lib/modules/4.17.0-rc5+/build/vmlinux
> Bytes read match those read by objdump
> Reading object code for memory address: 0xfffffe000005e01e
> thread__find_addr_map failed
> test child finished with -1
> ---- end ----
> Object code reading: FAILED!
> ---------------------------------------------------------------------------------------------------------->
> 
> $sudo ./perf test -vv 64
> 64: probe libc's inet_pton & backtrace it with ping       :
> --- start ---
> test child forked, pid 4751
> test child finished with -1
> ---- end ----
> probe libc's inet_pton & backtrace it with ping: FAILED!

there's been some recent discussion/changes in here, please follow:
  https://marc.info/?t=152662842600002&r=1&w=2

jirka