All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: zihan xi <zihanx@nebusec.ai>
Cc: netfilter-devel@vger.kernel.org, virtualization@lists.linux.dev,
	intel-wired-lan@lists.osuosl.org, bpf@vger.kernel.org,
	pablo@netfilter.org, phil@nwl.cc, davem@davemloft.net,
	edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
	kaber@trash.net, jengelh@medozas.de, andrew+netdev@lunn.ch,
	mst@redhat.com, jasowangio@gmail.com, eperezma@redhat.com,
	xuanzhuo@linux.alibaba.com, aleksander.lobakin@intel.com,
	ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
	john.fastabend@gmail.com, sdf@fomichev.me,
	magnus.karlsson@intel.com, maciej.fijalkowski@intel.com,
	willemb@google.com, alice.kernel@fastmail.im,
	eilaimemedsnaimel@gmail.com, imv4bel@gmail.com,
	shiming.cheng@mediatek.com, sd@queasysnail.net, vega@nebusec.ai,
	root@tr0jan.top
Subject: Re: [PATCH nf v8 0/3] netfilter: bound asynchronous packet duplication
Date: Fri, 16 Oct 2026 18:20:23 +0200	[thread overview]
Message-ID: <atJOxy1Q4twlJSJB@strlen.de> (raw)
In-Reply-To: <CAANe3eTSz3-EE0=9JNFBMFDqZ9NUfScHdi8EN30UVaTiRq0vcg@mail.gmail.com>

zihan xi <zihanx@nebusec.ai> wrote:
> I will send a one-patch v9 series for the NFQUEUE guard preservation
> only. It does not address netdev duplication or claim to provide a
> general facility for bounding every asynchronous duplication path.

makes sense to me, thanks!

      reply	other threads:[~2026-10-16 16:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  7:43 [PATCH nf v8 0/3] netfilter: bound asynchronous packet duplication Zihan Xi
2026-10-15  7:43 ` [PATCH nf v8 1/3] netfilter: nf_dup: preserve guard across NFQUEUE reinjection Zihan Xi
2026-10-15  7:56   ` sashiko-bot
2026-10-15  8:13     ` zihan xi
2026-10-15  7:43 ` [PATCH nf v8 2/3] netfilter: nf_dup_netdev: bound asynchronous duplication Zihan Xi
2026-10-15  7:58   ` sashiko-bot
2026-10-15  7:43 ` [PATCH nf v8 3/3] netfilter: nf_dup: prevent TTL and hop-limit underflow Zihan Xi
2026-10-15  7:51   ` sashiko-bot
2026-10-15  7:49 ` [PATCH nf v8 0/3] netfilter: bound asynchronous packet duplication netdev-bot+sinfo
2026-10-15 10:39 ` Florian Westphal
2026-10-15 11:33   ` zihan xi
2026-10-16 16:12   ` zihan xi
2026-10-16 16:20     ` Florian Westphal [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=atJOxy1Q4twlJSJB@strlen.de \
    --to=fw@strlen.de \
    --cc=aleksander.lobakin@intel.com \
    --cc=alice.kernel@fastmail.im \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=eilaimemedsnaimel@gmail.com \
    --cc=eperezma@redhat.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=imv4bel@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jasowangio@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=john.fastabend@gmail.com \
    --cc=kaber@trash.net \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=mst@redhat.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    --cc=root@tr0jan.top \
    --cc=sd@queasysnail.net \
    --cc=sdf@fomichev.me \
    --cc=shiming.cheng@mediatek.com \
    --cc=vega@nebusec.ai \
    --cc=virtualization@lists.linux.dev \
    --cc=willemb@google.com \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=zihanx@nebusec.ai \
    /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.