From: Eduard Zingerman <eddyz87@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>, memxor@gmail.com
Cc: puranjay@kernel.org, info@starlabs.sg, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/4] bpf: Mark pending sub-register zero extension before pruning a state
Date: Wed, 05 Aug 2026 13:36:15 -0700 [thread overview]
Message-ID: <bfe416825f7a03f599835a41d6c5d261c7b4432d.camel@gmail.com> (raw)
In-Reply-To: <785c9fa1-c238-47a5-b57f-23742cfaa728@iogearbox.net>
On Wed, 2026-08-05 at 21:54 +0200, Daniel Borkmann wrote:
> On 8/5/26 9:11 PM, Eduard Zingerman wrote:
> > On Wed, 2026-08-05 at 20:44 +0200, Daniel Borkmann wrote:
> [...]
> >
> > Hi Daniel,
> >
> > I have this series in progress:
> > https://lore.kernel.org/bpf/20260802-static-zext-v3-0-3456b2604574@gmail.com/
> > Fixing that exact issue. It needs one more iteration.
> Dang, missed it, integrating into liveness looks better, lets go with
> that. If the selftests from here are of any use, please feel free to
> pick and integrate into your respin.
Ack, will do!
next prev parent reply other threads:[~2026-08-05 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 18:44 [PATCH bpf-next 1/4] bpf: Mark pending sub-register zero extension before pruning a state Daniel Borkmann
2026-08-05 18:44 ` [PATCH bpf-next 2/4] bpf: Mark pending zero extension of arena ptrs " Daniel Borkmann
2026-08-05 18:44 ` [PATCH bpf-next 3/4] selftests/bpf: Add tests for sub-register zext across state pruning Daniel Borkmann
2026-08-05 18:44 ` [PATCH bpf-next 4/4] selftests/bpf: Add test for arena pointer " Daniel Borkmann
2026-08-05 20:14 ` sashiko-bot
2026-08-05 19:11 ` [PATCH bpf-next 1/4] bpf: Mark pending sub-register zero extension before pruning a state Eduard Zingerman
2026-08-05 19:54 ` Daniel Borkmann
2026-08-05 20:36 ` Eduard Zingerman [this message]
2026-08-05 20:22 ` sashiko-bot
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=bfe416825f7a03f599835a41d6c5d261c7b4432d.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=info@starlabs.sg \
--cc=memxor@gmail.com \
--cc=puranjay@kernel.org \
/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