[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKH8qBsfheXDP8Xj_UecdUyxta3jMEOzyue+=35DnENtF23o2g@mail.gmail.com>
Date: Thu, 22 Jun 2023 10:55:26 -0700
From: Stanislav Fomichev <sdf@...gle.com>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: bpf <bpf@...r.kernel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>, Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>, Song Liu <song@...nel.org>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Network Development <netdev@...r.kernel.org>
Subject: Re: [RFC bpf-next v2 02/11] bpf: Resolve single typedef when walking structs
On Wed, Jun 21, 2023 at 10:18 PM Alexei Starovoitov
<alexei.starovoitov@...il.com> wrote:
>
> On Wed, Jun 21, 2023 at 10:02 AM Stanislav Fomichev <sdf@...gle.com> wrote:
> >
> > It is impossible to use skb_frag_t in the tracing program. So let's
> > resolve a single typedef when walking the struct.
> >
> > Cc: netdev@...r.kernel.org
> > Signed-off-by: Stanislav Fomichev <sdf@...gle.com>
>
> Pls send this one separately without RFC, but with a selftest,
> so we can land it soon.
Sure, will do!
Powered by blists - more mailing lists