linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KP Singh <kpsingh@kernel.org>
To: Florent Revest <revest@chromium.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, kpsingh@chromium.org,
	Martin KaFai Lau <kafai@fb.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 2/4] bpf: Expose bpf_get_socket_cookie to tracing programs
Date: Wed, 9 Dec 2020 16:23:59 +0100	[thread overview]
Message-ID: <CANA3-0d_VqjXUc0LBwc1f7Js9NfV_ZRp8e=tQ-q5-EWjRsqFYg@mail.gmail.com> (raw)
In-Reply-To: <20201209132636.1545761-2-revest@chromium.org>

On Wed, Dec 9, 2020 at 2:29 PM Florent Revest <revest@chromium.org> wrote:
>
> This needs two new helpers, one that works in a sleepable context (using
> sock_gen_cookie which disables/enables preemption) and one that does not
> (for performance reasons). Both take a struct sock pointer and need to
> check it for NULLness.
>
> This helper could also be useful to other BPF program types such as LSM.
>
> Signed-off-by: Florent Revest <revest@chromium.org>

Acked-by: KP Singh <kpsingh@kernel.org>

  reply	other threads:[~2020-12-09 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 13:26 [PATCH bpf-next v4 1/4] bpf: Be less specific about socket cookies guarantees Florent Revest
2020-12-09 13:26 ` [PATCH bpf-next v4 2/4] bpf: Expose bpf_get_socket_cookie to tracing programs Florent Revest
2020-12-09 15:23   ` KP Singh [this message]
2020-12-09 16:35   ` Daniel Borkmann
2021-01-19 15:59     ` Florent Revest
2020-12-09 13:26 ` [PATCH bpf-next v4 3/4] selftests/bpf: Integrate the socket_cookie test to test_progs Florent Revest
2020-12-09 13:26 ` [PATCH bpf-next v4 4/4] selftests/bpf: Add a selftest for the tracing bpf_get_socket_cookie Florent Revest

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANA3-0d_VqjXUc0LBwc1f7Js9NfV_ZRp8e=tQ-q5-EWjRsqFYg@mail.gmail.com' \
    --to=kpsingh@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=revest@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).