[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220203174010.GA16681@lst.de>
Date: Thu, 3 Feb 2022 18:40:10 +0100
From: Christoph Hellwig <hch@....de>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Christoph Hellwig <hch@....de>, Jonathan Corbet <corbet@....net>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Network Development <netdev@...r.kernel.org>,
bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH 3/5] bpf, docs: Better document the legacy packet
access instruction
On Thu, Feb 03, 2022 at 09:32:38AM -0800, Alexei Starovoitov wrote:
> These two places make it sound like it's interpreter only behavior.
> I've reworded it like:
> -the interpreter context is a pointer to networking packet. ``BPF_ABS``
> +the program context is a pointer to networking packet. ``BPF_ABS``
>
> -interpreter will abort the execution of the program.
> +program execution will be aborted.
>
> and pushed to bpf-next with the rest of patches.
The interpreter thing is actually unchanged from the old text, but I
totally agree with your fixup. Thanks!
Powered by blists - more mailing lists