From: Florian Westphal <fw@strlen.de>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: netfilter-devel@vger.kernel.org, Seesee <cjc000013@gmail.com>
Subject: Re: [PATCH nf] netfilter: nft_set_pipapo: don't leak bad clone into future transaction
Date: Wed, 24 Jun 2026 22:56:12 +0200 [thread overview]
Message-ID: <ajxEbCY0yNsrsxx6@strlen.de> (raw)
In-Reply-To: <ajJUklUUmvafRVi9@strlen.de>
Florian Westphal <fw@strlen.de> wrote:
> Stefano Brivio <sbrivio@redhat.com> wrote:
> > I can try to get to this in the next few days (I would have some ideas
> > about testing, see below), but I suppose we want a fix quickly if that's
> > really the case so I'm actually fine with this, with one nit, also
> > reported below.
>
> I don't mind, this can wait if you prefer to undo the state.
Ping. Are you working on an alternative patch or should I send a v2?
next prev parent reply other threads:[~2026-06-24 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 19:19 [PATCH nf] netfilter: nft_set_pipapo: don't leak bad clone into future transaction Florian Westphal
2026-06-17 5:51 ` Stefano Brivio
2026-06-17 8:02 ` Florian Westphal
2026-06-24 20:56 ` Florian Westphal [this message]
2026-06-24 21:22 ` Stefano Brivio
2026-06-24 21:31 ` Florian Westphal
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=ajxEbCY0yNsrsxx6@strlen.de \
--to=fw@strlen.de \
--cc=cjc000013@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=sbrivio@redhat.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