| 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
| ||
|
Date: Tue, 22 Dec 2015 22:16:42 +0800 From: "Wangnan (F)" <wangnan0@...wei.com> To: Will Deacon <will.deacon@....com> CC: <guohanjun@...wei.com>, Jiri Olsa <jolsa@...nel.org>, <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, pi3orama <pi3orama@....com>, xiakaixu 00238161 <xiakaixu@...wei.com> Subject: Re: [BUG REPORT]: ARM64: perf: System hung in perf test On 2015/12/21 22:01, Will Deacon wrote: > On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote: > [SNIP] >> # /perf test -v signal >> 17: Test breakpoint overflow signal handler : >> --- start --- >> test child forked, pid 792 >> count1 11, count2 11, overflow 11 >> failed: RF EFLAG recursion issue detected >> failed: wrong overflow hit >> failed: wrong count for bp2 >> test child finished with -1 >> ---- end ---- >> Test breakpoint overflow signal handler: FAILED! > ... and this sounds like the perf tool expecting to single-step over > signal handlers, whereas (on arm64) we deliberately single-step into > them, so you can run into a loop for this case. Could you please provide me more information? Do you think it is a kernel bug and should be fixed? Or it is an invalid testcase for aarch64? Thank you. > Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists