All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	pablo@netfilter.org, phil@nwl.cc
Subject: Re: [PATCH 0/3 nf-next] netfilter: synproxy: timestamp adjustment fixes
Date: Sun, 24 May 2026 19:16:04 +0200	[thread overview]
Message-ID: <ahMyVJYynOoa32U5@strlen.de> (raw)
In-Reply-To: <7dcb73cb-11ab-4c9d-89bd-7418bdc86fdb@suse.de>

Fernando Fernandez Mancera <fmancera@suse.de> wrote:
> What do you all think? nf or nf-next for the 4 commits? I tried to reproduce
> an UAF but couldn't trigger it. Although, I was able to write to the stale
> pointer using tc mirred..

nf.  But I'm not sold on this series: dropping patckets outside
of rulesets should be a last resort.

  reply	other threads:[~2026-05-24 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23 19:47 [PATCH 0/3 nf-next] netfilter: synproxy: timestamp adjustment fixes Fernando Fernandez Mancera
2026-05-23 19:47 ` [PATCH 1/3 nf-next] netfilter: synproxy: drop packets if timestamp adjustment fails Fernando Fernandez Mancera
2026-05-23 19:47 ` [PATCH 2/3 nf-next] netfilter: synproxy: drop packets with duplicated timestamp options Fernando Fernandez Mancera
2026-05-23 19:47 ` [PATCH 3/3 nf-next] netfilter: synproxy: fix unaligned memory access in timestamp adjustment Fernando Fernandez Mancera
2026-05-24 16:58 ` [PATCH 0/3 nf-next] netfilter: synproxy: timestamp adjustment fixes Fernando Fernandez Mancera
2026-05-24 17:16   ` Florian Westphal [this message]
2026-05-24 18:48     ` Fernando Fernandez Mancera
2026-05-24 19:24       ` Florian Westphal
2026-05-24 21:24         ` Fernando Fernandez Mancera

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=ahMyVJYynOoa32U5@strlen.de \
    --to=fw@strlen.de \
    --cc=coreteam@netfilter.org \
    --cc=fmancera@suse.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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 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.