linux-kernel - Re: [RFC 0/1] BPF tracing for arm64 using fprobe

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:   Mon, 21 Nov 2022 15:23:00 +0100
From:   KP Singh <kpsingh@...nel.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Chris Mason <clm@...a.com>, Steven Rostedt <rostedt@...dmis.org>,
        Mark Rutland <mark.rutland@....com>,
        Alexei Starovoitov <alexei.starovoitov@...il.com>,
        Florent Revest <revest@...omium.org>,
        bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii@...nel.org>,
        Brendan Jackman <jackmanb@...gle.com>, markowsky@...gle.com,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Xu Kuohai <xukuohai@...wei.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Christoph Hellwig <hch@...radead.org>
Subject: Re: [RFC 0/1] BPF tracing for arm64 using fprobe

On Mon, Nov 21, 2022 at 3:17 PM Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Mon, Nov 21, 2022 at 02:47:10PM +0100, KP Singh wrote:
>
> > > > How do I know that a function return was modified by BPF? If I'm debugging
> >
> > You can list the BPF programs that are loaded in the kernel with
> >
> > # bpftool prog list
>
> Only when you have access to the machine; most cases it's people sending
> random splats by email.

Good point, What about having information about loaded BPF programs in the
kernel stack traces and sharing bytecode, somehow, like in crash dumps?

>
> > Also, the BPF programs show up in call stacks when you are debugging.
>
> Only when it splats inside the BPF part, not when it splats after
> because BPF changed semantics of a function.
>
>