From: patchwork-bot+netdevbpf@kernel.org
To: Luis Gerhorst <gerhorst@cs.fau.de>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, andreimatei1@gmail.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bpf: remove misleading spec_v1 check on var-offset stack read
Date: Thu, 16 Mar 2023 21:10:18 +0000 [thread overview]
Message-ID: <167900101816.1695.823827696670320072.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230315165358.23701-1-gerhorst@cs.fau.de>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 15 Mar 2023 17:54:00 +0100 you wrote:
> For every BPF_ADD/SUB involving a pointer, adjust_ptr_min_max_vals()
> ensures that the resulting pointer has a constant offset if
> bypass_spec_v1 is false. This is ensured by calling
> sanitize_check_bounds() which in turn calls
> check_stack_access_for_ptr_arithmetic(). There, -EACCESS is returned if
> the register's offset is not constant, thereby rejecting the program.
>
> [...]
Here is the summary with links:
- bpf: remove misleading spec_v1 check on var-offset stack read
https://git.kernel.org/bpf/bpf-next/c/082cdc69a465
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-16 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 16:51 bpf: misleading spec_v1 check on variable-offset stack read? Luis Gerhorst
2023-03-15 16:54 ` [PATCH] bpf: remove misleading spec_v1 check on var-offset stack read Luis Gerhorst
2023-03-16 21:10 ` 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=167900101816.1695.823827696670320072.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andreimatei1@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gerhorst@cs.fau.de \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@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
all inboxes | Powered by JetHome®