From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Antonio Ojea <aojea@google.com>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v2 1/2] netfilter: nf_queue: limit the hook drop flush to the unregistered hook point
Date: Wed, 21 Oct 2026 09:40:34 +0200 [thread overview]
Message-ID: <athscka5B9UmNsJz@strlen.de> (raw)
In-Reply-To: <atfxlqHrKr3n3Qy3@chamomile>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Fri, Oct 16, 2026 at 01:33:04PM +0000, Antonio Ojea wrote:
> > Is there a chance to pick it up for nf-next before the 7.4 merge window,
> > or do you prefer that I resend once 7.4-rc1 is out?
>
> This is now in the net-next tree:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=5d1b850ea3f6e6ba2090ebc437e9bbec1d7e5ae4
>
> according to:
>
> https://lore.kernel.org/netfilter-devel/atXgURtsFB4UFXES@chamomile/T/#u
>
> this needs a follow up. Florian, please, confirm this.
Yes, this needs a followup, both br_netfilter and conntrack should
flush nfqueued packets explicitly.
Antonio, could you make such a patch? Thanks.
next prev parent reply other threads:[~2026-10-21 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 18:58 [PATCH nf-next v2 1/2] netfilter: nf_queue: limit the hook drop flush to the unregistered hook point Antonio Ojea
2026-09-28 18:58 ` [PATCH nf-next v2 2/2] selftests: netfilter: nft_queue: check the scope of the hook drop flush Antonio Ojea
2026-10-16 13:33 ` [PATCH nf-next v2 1/2] netfilter: nf_queue: limit the hook drop flush to the unregistered hook point Antonio Ojea
2026-10-16 14:13 ` Florian Westphal
2026-10-20 22:56 ` Pablo Neira Ayuso
2026-10-21 7:40 ` Florian Westphal [this message]
2026-10-21 14:57 ` Antonio Ojea
2026-10-21 19:43 ` Antonio Ojea
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=athscka5B9UmNsJz@strlen.de \
--to=fw@strlen.de \
--cc=aojea@google.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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