From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
fw@strlen.de, phil@nwl.cc
Subject: Re: [PATCH 0/5 nf-next v4] netfilter: synproxy: misc fixes about synproxy core
Date: Thu, 28 May 2026 00:24:14 +0200 [thread overview]
Message-ID: <ahdvDhDXmPjh1kZ3@chamomile> (raw)
In-Reply-To: <e610bace-a04a-4f6c-bea6-3e9d6646352a@suse.de>
On Wed, May 27, 2026 at 04:10:36PM +0200, Fernando Fernandez Mancera wrote:
> On 5/26/26 11:58 PM, Fernando Fernandez Mancera wrote:
> > This series fixes several long standing issues during synproxy timestamp
> > adjustment and concurrent hook registration. From ignored error handling
> > to unaligned memory access. Most of this are not issues impacting real
> > setups as they would have been reported before.
> >
> > FWIW; I am sending these fixes as separated patches because they are
> > addressing independent issues.
> >
> > Fernando Fernandez Mancera (5):
> > netfilter: synproxy: drop packets if timestamp adjustment fails
> > netfilter: synproxy: adjust duplicate timestamp options
> > netfilter: synproxy: fix unaligned memory access in timestamp
> > adjustment
> > netfilter: synproxy: protect nf_ct_seqadj_init() with conntrack lock
>
> Sashiko pointed out another issue around nf_ct_seqadj_init() not related to
> these patches. Could we get this merged (if it looks good) and the move
> forward with a follow-up? I am afraid of pilling up a series that it is too
> big.
>
> Any thoughts?
>
> P.S: I am owning the follow-up I just want to reduce the complexity of
> getting everything merged together.
Follow up should be fine, thanks Fernando.
prev parent reply other threads:[~2026-05-27 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 21:58 [PATCH 0/5 nf-next v4] netfilter: synproxy: misc fixes about synproxy core Fernando Fernandez Mancera
2026-05-26 21:58 ` [PATCH 1/5 nf-next v4] netfilter: synproxy: drop packets if timestamp adjustment fails Fernando Fernandez Mancera
2026-05-26 21:58 ` [PATCH 2/5 nf-next v4] netfilter: synproxy: adjust duplicate timestamp options Fernando Fernandez Mancera
2026-05-26 21:58 ` [PATCH 3/5 nf-next v4] netfilter: synproxy: fix unaligned memory access in timestamp adjustment Fernando Fernandez Mancera
2026-05-26 21:58 ` [PATCH 4/5 nf-next v4] netfilter: synproxy: protect nf_ct_seqadj_init() with conntrack lock Fernando Fernandez Mancera
2026-05-26 21:58 ` [PATCH 5/5 nf-next v4] netfilter: synproxy: add mutex to guard hook reference counting Fernando Fernandez Mancera
2026-05-27 14:10 ` [PATCH 0/5 nf-next v4] netfilter: synproxy: misc fixes about synproxy core Fernando Fernandez Mancera
2026-05-27 22:24 ` Pablo Neira Ayuso [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=ahdvDhDXmPjh1kZ3@chamomile \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fmancera@suse.de \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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