[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7o5espvlmyttj74awibexz3q7dkvrerswgsn3x7vxesjxf5ggu@urrrltbmsqir>
Date: Fri, 29 Mar 2024 14:53:18 +0800
From: Shung-Hsi Yu <shung-hsi.yu@...e.com>
To: Harishankar Vishwanathan <harishankar.vishwanathan@...il.com>
Cc: ast@...nel.org, harishankar.vishwanathan@...gers.edu,
sn624@...rutgers.edu, sn349@...rutgers.edu, m.shachnai@...gers.edu, paul@...valent.com,
Srinivas Narayana <srinivas.narayana@...gers.edu>, Santosh Nagarakatte <santosh.nagarakatte@...gers.edu>,
Daniel Borkmann <daniel@...earbox.net>, John Fastabend <john.fastabend@...il.com>,
Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard Zingerman <eddyz87@...il.com>, Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>, KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>, Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH bpf-next] Fix latent unsoundness in and/or/xor value
tracking
On Fri, Mar 29, 2024 at 02:34:00PM +0800, Shung-Hsi Yu wrote:
> [...]
> Fixed: b03c9f9fdc37 ("bpf/verifier: track signed and unsigned min/max values")
Should have been
Fixes: b03c9f9fdc37 ("bpf/verifier: track signed and unsigned min/max values")
Sorry for the noise.
Powered by blists - more mailing lists