Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190426184951.21812-1-mmullins@fb.com>
In-Reply-To: <20190426184951.21812-1-mmullins@fb.com>
From:   Alexei Starovoitov <alexei.starovoitov@gmail.com>
Date:   Fri, 26 Apr 2019 19:15:14 -0700
Message-ID: <CAADnVQJuxuLC8uzSz1UWDQa3txc+aRdw4OkUmdBOjdezkUhd+A@mail.gmail.com>
Subject: Re: [PATCH bpf-next v5 0/5] writable contexts for bpf raw tracepoints
To:     Matt Mullins <mmullins@fb.com>
Cc:     Andrew Hall <hall@fb.com>, Alexei Starovoitov <ast@kernel.org>,
        bpf <bpf@vger.kernel.org>,
        Network Development <netdev@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Martin KaFai Lau <kafai@fb.com>,
        Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Apr 26, 2019 at 11:50 AM Matt Mullins <mmullins@fb.com> wrote:
>
> This adds an opt-in interface for tracepoints to expose a writable context to
> BPF_PROG_TYPE_RAW_TRACEPOINT_WRITABLE programs that are attached, while
> supporting read-only access from existing BPF_PROG_TYPE_RAW_TRACEPOINT
> programs, as well as from non-BPF-based tracepoints.
>
> The initial motivation is to support tracing that can be observed from the
> remote end of an NBD socket, e.g. by adding flags to the struct nbd_request
> header.  Earlier attempts included adding an NBD-specific tracepoint fd, but in
> code review, I was recommended to implement it more generically -- as a result,
> this patchset is far simpler than my initial try.
>
> v4->v5:
>   * rebased onto bpf-next/master and fixed merge conflicts
>   * "tools: sync bpf.h" also syncs comments that have previously changed
>     in bpf-next

Applied. Thanks!