From: patchwork-bot+netdevbpf@kernel.org
To: Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>
Cc: ast@kernel.org, harishankar.vishwanathan@rutgers.edu,
sn624@cs.rutgers.edu, sn349@cs.rutgers.edu,
m.shachnai@rutgers.edu, paul@isovalent.com,
srinivas.narayana@rutgers.edu, santosh.nagarakatte@rutgers.edu,
daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 bpf-next] bpf: Harden and/or/xor value tracking
Date: Tue, 16 Apr 2024 16:00:28 +0000 [thread overview]
Message-ID: <171328322834.16684.6567796200399765338.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240416115303.331688-1-harishankar.vishwanathan@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 16 Apr 2024 07:53:02 -0400 you wrote:
> This patch addresses a latent unsoundness issue in the
> scalar(32)_min_max_and/or/xor functions. While it is not a bugfix, it
> ensures that the functions produce sound outputs for all inputs.
>
> The issue occurs in these functions when setting signed bounds. The
> following example illustrates the issue for scalar_min_max_and(), but it
> applies to the other functions.
>
> [...]
Here is the summary with links:
- [v3,bpf-next] bpf: Harden and/or/xor value tracking
https://git.kernel.org/bpf/bpf-next/c/1f586614f3ff
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:[~2024-04-16 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 11:53 [PATCH v3 bpf-next] bpf: Harden and/or/xor value tracking Harishankar Vishwanathan
2024-04-16 16: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=171328322834.16684.6567796200399765338.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=haoluo@google.com \
--cc=harishankar.vishwanathan@gmail.com \
--cc=harishankar.vishwanathan@rutgers.edu \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.shachnai@rutgers.edu \
--cc=martin.lau@linux.dev \
--cc=paul@isovalent.com \
--cc=santosh.nagarakatte@rutgers.edu \
--cc=sdf@google.com \
--cc=sn349@cs.rutgers.edu \
--cc=sn624@cs.rutgers.edu \
--cc=song@kernel.org \
--cc=srinivas.narayana@rutgers.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.