mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jerome Marchand <jmarchan@redhat.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, yonghong.song@linux.dev,
	eddyz87@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] bpf: Specify access type of bpf_sysctl_get_name args
Date: Tue, 24 Jun 2025 05:00:08 +0000	[thread overview]
Message-ID: <175074120875.3399614.10605130442249512213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250619140603.148942-1-jmarchan@redhat.com>

Hello:

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

On Thu, 19 Jun 2025 16:06:01 +0200 you wrote:
> The second argument of bpf_sysctl_get_name() helper is a pointer to a
> buffer that is being written to. However that isn't specify in the
> prototype. Until commit 37cce22dbd51a ("bpf: verifier: Refactor helper
> access type tracking") that mistake was hidden by the way the verifier
> treated helper accesses. Since then, the verifier, working on wrong
> infromation from the prototype, can make faulty optimization that
> would had been caught by the test_sysctl selftests if it was run by
> the CI.
> 
> [...]

Here is the summary with links:
  - [v3,1/2] bpf: Specify access type of bpf_sysctl_get_name args
    https://git.kernel.org/bpf/bpf/c/2eb7648558a7
  - [v3,2/2] selftests/bpf: Convert test_sysctl to prog_tests
    https://git.kernel.org/bpf/bpf/c/b8a205486ed5

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-06-24  4:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 14:06 Jerome Marchand
2025-06-19 14:06 ` [PATCH v3 1/2] " Jerome Marchand
2025-06-19 17:32   ` Yonghong Song
2025-06-19 14:06 ` [PATCH v3 2/2] selftests/bpf: Convert test_sysctl to prog_tests Jerome Marchand
2025-06-19 17:33   ` Yonghong Song
2025-06-24  5: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=175074120875.3399614.10605130442249512213.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=jmarchan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --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
all inboxes | Powered by JetHome®