public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@linux.dev, davemarchevsky@fb.com
Subject: Re: [PATCH bpf-next v1 0/2] Fix for check_func_arg_reg_off
Date: Tue, 22 Aug 2023 20:00:24 +0000	[thread overview]
Message-ID: <169273442414.14630.2899573532504343892.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230822175140.1317749-1-memxor@gmail.com>

Hello:

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

On Tue, 22 Aug 2023 23:21:38 +0530 you wrote:
> Remove a leftover hunk in check_func_arg_reg_off that incorrectly
> bypasses reg->off == 0 requirement for release kfuncs and helpers.
> 
> Kumar Kartikeya Dwivedi (2):
>   bpf: Fix check_func_arg_reg_off bug for graph root/node
>   selftests/bpf: Add test for bpf_obj_drop with bad reg->off
> 
> [...]

Here is the summary with links:
  - [bpf-next,v1,1/2] bpf: Fix check_func_arg_reg_off bug for graph root/node
    https://git.kernel.org/bpf/bpf-next/c/6785b2edf48c
  - [bpf-next,v1,2/2] selftests/bpf: Add test for bpf_obj_drop with bad reg->off
    https://git.kernel.org/bpf/bpf-next/c/fbc5bc4c8e6c

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



      parent reply	other threads:[~2023-08-22 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 17:51 [PATCH bpf-next v1 0/2] Fix for check_func_arg_reg_off Kumar Kartikeya Dwivedi
2023-08-22 17:51 ` [PATCH bpf-next v1 1/2] bpf: Fix check_func_arg_reg_off bug for graph root/node Kumar Kartikeya Dwivedi
2023-08-22 17:51 ` [PATCH bpf-next v1 2/2] selftests/bpf: Add test for bpf_obj_drop with bad reg->off Kumar Kartikeya Dwivedi
2023-08-22 20:00 ` 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=169273442414.14630.2899573532504343892.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=davemarchevsky@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.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