linux-kernel - Re: [PATCH] perf powerpc: Don't call perf_event

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 04 Oct 2016 15:08:27 +1100
From:   Michael Ellerman <mpe@...erman.id.au>
To:     Jiri Olsa <jolsa@...nel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:     lkml <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Michael Neuling <mikey@...ling.org>,
        Paul Mackerras <paulus@...ba.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Jan Stancek <jstancek@...hat.com>
Subject: Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

Jiri Olsa <jolsa@...nel.org> writes:

> The trinity syscall fuzzer triggered following WARN on powerpc:
>   WARNING: CPU: 9 PID: 2998 at arch/powerpc/kernel/hw_breakpoint.c:278
>   ...
>   NIP [c00000000093aedc] .hw_breakpoint_handler+0x28c/0x2b0
>   LR [c00000000093aed8] .hw_breakpoint_handler+0x288/0x2b0
>   Call Trace:
>   [c0000002f7933580] [c00000000093aed8] .hw_breakpoint_handler+0x288/0x2b0 (unreliable)
>   [c0000002f7933630] [c0000000000f671c] .notifier_call_chain+0x7c/0xf0
>   [c0000002f79336d0] [c0000000000f6abc] .__atomic_notifier_call_chain+0xbc/0x1c0
>   [c0000002f7933780] [c0000000000f6c40] .notify_die+0x70/0xd0
>   [c0000002f7933820] [c00000000001a74c] .do_break+0x4c/0x100
>   [c0000002f7933920] [c0000000000089fc] handle_dabr_fault+0x14/0x48

Is that the full stack trace? It doesn't look like it.

And were you running trinity as root or regular user?

cheers