linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xu Kuohai <xukuohai@huaweicloud.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
	linux-security-module@vger.kernel.org, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, eddyz87@gmail.com,
	shung-hsi.yu@suse.com, yonghong.song@linux.dev,
	kpsingh@kernel.org, roberto.sassu@huawei.com,
	mattbobrowski@google.com, laoar.shao@gmail.com,
	iii@linux.ibm.com, jose.marchesi@oracle.com,
	jamorris@linux.microsoft.com, kees@kernel.org,
	jackmanb@google.com, revest@google.com
Subject: Re: [PATCH bpf-next v2 0/9] Add BPF LSM return value range check, BPF part
Date: Tue, 23 Jul 2024 00:50:35 +0000	[thread overview]
Message-ID: <172169583505.13320.286982146467311269.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240719110059.797546-1-xukuohai@huaweicloud.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 19 Jul 2024 19:00:50 +0800 you wrote:
> From: Xu Kuohai <xukuohai@huawei.com>
> 
> LSM BPF prog may make kernel panic when returning an unexpected value,
> such as returning positive value on hook file_alloc_security.
> 
> To fix it, series [1] refactored LSM hook return values and added
> BPF return value check on top of that. Since the refactoring of LSM
> hooks and checking BPF prog return value patches is not closely related,
> this series separates BPF-related patches from [1].
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/9] bpf, lsm: Add disabled BPF LSM hook list
    https://git.kernel.org/bpf/bpf-next/c/afe4588df73f
  - [bpf-next,v2,2/9] bpf, lsm: Add check for BPF LSM return value
    https://git.kernel.org/bpf/bpf-next/c/af980eb89f06
  - [bpf-next,v2,3/9] bpf: Prevent tail call between progs attached to different hooks
    https://git.kernel.org/bpf/bpf-next/c/b39ffa50b415
  - [bpf-next,v2,4/9] bpf: Fix compare error in function retval_range_within
    https://git.kernel.org/bpf/bpf-next/c/9e14de5b9c12
  - [bpf-next,v2,5/9] bpf, verifier: improve signed ranges inference for BPF_AND
    (no matching commit)
  - [bpf-next,v2,6/9] selftests/bpf: Avoid load failure for token_lsm.c
    https://git.kernel.org/bpf/bpf-next/c/f81ad29cdf88
  - [bpf-next,v2,7/9] selftests/bpf: Add return value checks for failed tests
    https://git.kernel.org/bpf/bpf-next/c/fc2baf1730f9
  - [bpf-next,v2,8/9] selftests/bpf: Add test for lsm tail call
    https://git.kernel.org/bpf/bpf-next/c/2f56fae88135
  - [bpf-next,v2,9/9] selftests/bpf: Add verifier tests for bpf lsm
    https://git.kernel.org/bpf/bpf-next/c/cc1bfd52e4ca

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-07-23  0:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 11:00 [PATCH bpf-next v2 0/9] Add BPF LSM return value range check, BPF part Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 1/9] bpf, lsm: Add disabled BPF LSM hook list Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 2/9] bpf, lsm: Add check for BPF LSM return value Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 3/9] bpf: Prevent tail call between progs attached to different hooks Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 4/9] bpf: Fix compare error in function retval_range_within Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 5/9] bpf, verifier: improve signed ranges inference for BPF_AND Xu Kuohai
2024-07-22  7:13   ` Eduard Zingerman
2024-07-22 12:57     ` Shung-Hsi Yu
2024-07-22 18:47       ` Eduard Zingerman
2024-07-23  0:48         ` Alexei Starovoitov
2024-07-23  6:36           ` Shung-Hsi Yu
2024-07-23  7:07             ` Shung-Hsi Yu
2024-07-24  1:17               ` Alexei Starovoitov
2024-07-19 11:00 ` [PATCH bpf-next v2 6/9] selftests/bpf: Avoid load failure for token_lsm.c Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 7/9] selftests/bpf: Add return value checks for failed tests Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 8/9] selftests/bpf: Add test for lsm tail call Xu Kuohai
2024-07-19 11:00 ` [PATCH bpf-next v2 9/9] selftests/bpf: Add verifier tests for bpf lsm Xu Kuohai
2024-07-23  0:50 ` patchwork-bot+netdevbpf [this message]

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=172169583505.13320.286982146467311269.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=iii@linux.ibm.com \
    --cc=jackmanb@google.com \
    --cc=jamorris@linux.microsoft.com \
    --cc=jose.marchesi@oracle.com \
    --cc=kees@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mattbobrowski@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=revest@google.com \
    --cc=roberto.sassu@huawei.com \
    --cc=shung-hsi.yu@suse.com \
    --cc=xukuohai@huaweicloud.com \
    --cc=yonghong.song@linux.dev \
    /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).