[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQKtu1=ybxbzLQUMZQz3pwNJVjB+18t0vAhGAb=6kK8UbQ@mail.gmail.com>
Date: Thu, 25 Jul 2024 09:51:43 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Manjusaka <me@...jusaka.me>
Cc: Yonghong Song <yonghong.song@...ux.dev>, Leon Hwang <hffilwlqm@...il.com>,
Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>,
John Fastabend <john.fastabend@...il.com>, Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>, Eduard Zingerman <eddyz87@...il.com>, Song Liu <song@...nel.org>,
KP Singh <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>, Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>, bpf <bpf@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH bpf-next v2] bpf: Add bpf_check_attach_target_with_klog
method to output failure logs to kernel
On Wed, Jul 24, 2024 at 11:33 PM Manjusaka <me@...jusaka.me> wrote:
>
> Actually, for personally, I think it would be better to get the error message from dmesg.
This is a non-starter. We're not going to pollute dmesg with
verifier messages.
Powered by blists - more mailing lists