public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	alexei.starovoitov@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH] bpf: Refactor check_ctx_access()
Date: Sun, 23 Feb 2025 20:30:46 +0000	[thread overview]
Message-ID: <174034264676.2612491.11796681762886469056.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250221175644.1822383-1-ameryhung@gmail.com>

Hello:

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

On Fri, 21 Feb 2025 09:56:44 -0800 you wrote:
> Reduce the variable passing madness surrounding check_ctx_access().
> Currently, check_mem_access() passes many pointers to local variables to
> check_ctx_access(). They are used to initialize "struct
> bpf_insn_access_aux info" in check_ctx_access() and then passed to
> is_valid_access(). Then, check_ctx_access() takes the data our from
> info and write them back the pointers to pass them back. This can be
> simpilified by moving info up to check_mem_access().
> 
> [...]

Here is the summary with links:
  - bpf: Refactor check_ctx_access()
    https://git.kernel.org/bpf/bpf-next/c/201b62ccc831

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



      parent reply	other threads:[~2025-02-23 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 17:56 [PATCH] bpf: Refactor check_ctx_access() Amery Hung
2025-02-23 20:23 ` Alexei Starovoitov
2025-02-23 20:30 ` 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=174034264676.2612491.11796681762886469056.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@meta.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