[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <677dc8f7-d4e9-7717-5def-935340a23cd2@iogearbox.net>
Date: Tue, 23 Jun 2020 17:29:37 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Song Liu <songliubraving@...com>, bpf@...r.kernel.org,
netdev@...r.kernel.org
Cc: ast@...nel.org, kernel-team@...com, john.fastabend@...il.com,
kpsingh@...omium.org
Subject: Re: [PATCH bpf-next 2/3] bpf: allow %pB in bpf_seq_printf()
On 6/23/20 9:08 AM, Song Liu wrote:
> This makes it easy to dump stack trace with bpf_seq_printf().
>
> Signed-off-by: Song Liu <songliubraving@...com>
> ---
> kernel/trace/bpf_trace.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/trace/bpf_trace.c b/kernel/trace/bpf_trace.c
> index 2c13bcb5c2bce..ced3176801ae8 100644
> --- a/kernel/trace/bpf_trace.c
> +++ b/kernel/trace/bpf_trace.c
> @@ -636,7 +636,8 @@ BPF_CALL_5(bpf_seq_printf, struct seq_file *, m, char *, fmt, u32, fmt_size,
> if (fmt[i] == 'p') {
> if (fmt[i + 1] == 0 ||
> fmt[i + 1] == 'K' ||
> - fmt[i + 1] == 'x') {
> + fmt[i + 1] == 'x' ||
> + fmt[i + 1] == 'B') {
> /* just kernel pointers */
> params[fmt_cnt] = args[fmt_cnt];
> fmt_cnt++;
>
Why only bpf_seq_printf(), what about bpf_trace_printk()?
Powered by blists - more mailing lists