From: patchwork-bot+netdevbpf@kernel.org
To: KP Singh <kpsingh@chromium.org>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
songliubraving@fb.com, kafai@fb.com, ast@kernel.org,
daniel@iogearbox.net, pjt@google.com, jannh@google.com,
haoluo@google.com
Subject: Re: [PATCH bpf-next v6 1/9] bpf: Allow LSM programs to use bpf spin locks
Date: Fri, 06 Nov 2020 16:30:06 +0000 [thread overview]
Message-ID: <160468020631.12149.17904247795919763724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201106103747.2780972-2-kpsingh@chromium.org>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 6 Nov 2020 10:37:39 +0000 you wrote:
> From: KP Singh <kpsingh@google.com>
>
> Usage of spin locks was not allowed for tracing programs due to
> insufficient preemption checks. The verifier does not currently prevent
> LSM programs from using spin locks, but the helpers are not exposed
> via bpf_lsm_func_proto.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/9] bpf: Allow LSM programs to use bpf spin locks
https://git.kernel.org/bpf/bpf-next/c/9e7a4d9831e8
- [bpf-next,v6,2/9] bpf: Implement task local storage
https://git.kernel.org/bpf/bpf-next/c/4cf1bc1f1045
- [bpf-next,v6,3/9] libbpf: Add support for task local storage
https://git.kernel.org/bpf/bpf-next/c/8885274d2259
- [bpf-next,v6,4/9] bpftool: Add support for task local storage
https://git.kernel.org/bpf/bpf-next/c/864ab0616dcc
- [bpf-next,v6,5/9] bpf: Implement get_current_task_btf and RET_PTR_TO_BTF_ID
https://git.kernel.org/bpf/bpf-next/c/3ca1032ab7ab
- [bpf-next,v6,6/9] bpf: Fix tests for local_storage
https://git.kernel.org/bpf/bpf-next/c/f0e5ba0bc481
- [bpf-next,v6,7/9] bpf: Update selftests for local_storage to use vmlinux.h
https://git.kernel.org/bpf/bpf-next/c/a367efa71b3f
- [bpf-next,v6,8/9] bpf: Add tests for task_local_storage
https://git.kernel.org/bpf/bpf-next/c/9cde3beeadb3
- [bpf-next,v6,9/9] bpf: Exercise syscall operations for inode and sk storage
https://git.kernel.org/bpf/bpf-next/c/4170bc6baa54
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-11-06 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 10:37 [PATCH bpf-next v6 0/9] Implement task_local_storage KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 1/9] bpf: Allow LSM programs to use bpf spin locks KP Singh
2020-11-06 16:30 ` patchwork-bot+netdevbpf [this message]
2020-11-06 10:37 ` [PATCH bpf-next v6 2/9] bpf: Implement task local storage KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 3/9] libbpf: Add support for " KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 4/9] bpftool: " KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 5/9] bpf: Implement get_current_task_btf and RET_PTR_TO_BTF_ID KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 6/9] bpf: Fix tests for local_storage KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 7/9] bpf: Update selftests for local_storage to use vmlinux.h KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 8/9] bpf: Add tests for task_local_storage KP Singh
2020-11-06 10:37 ` [PATCH bpf-next v6 9/9] bpf: Exercise syscall operations for inode and sk storage KP Singh
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=160468020631.12149.17904247795919763724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jannh@google.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjt@google.com \
--cc=songliubraving@fb.com \
/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