All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, fw@strlen.de, pablo@netfilter.org,
	kadlec@netfilter.org
Subject: Re: [PATCH net 0/2] ipv4: Ensure ECN bits don't influence source address validation
Date: Tue, 19 Jan 2021 22:30:08 +0000	[thread overview]
Message-ID: <161109540897.8518.1356785481446630724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1610790904.git.gnault@redhat.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Sat, 16 Jan 2021 11:44:18 +0100 you wrote:
> Functions that end up calling fib_table_lookup() should clear the ECN
> bits from the TOS, otherwise ECT(0) and ECT(1) packets can be treated
> differently.
> 
> Most functions already clear the ECN bits, but there are a few cases
> where this is not done. This series only fixes the ones related to
> source address validation.
> 
> [...]

Here is the summary with links:
  - [net,1/2] udp: mask TOS bits in udp_v4_early_demux()
    https://git.kernel.org/netdev/net/c/8d2b51b008c2
  - [net,2/2] netfilter: rpfilter: mask ecn bits before fib lookup
    https://git.kernel.org/netdev/net/c/2e5a6266fbb1

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-01-19 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 10:44 [PATCH net 0/2] ipv4: Ensure ECN bits don't influence source address validation Guillaume Nault
2021-01-16 10:44 ` [PATCH net 1/2] udp: mask TOS bits in udp_v4_early_demux() Guillaume Nault
2021-01-16 10:44 ` [PATCH net 2/2] netfilter: rpfilter: mask ecn bits before fib lookup Guillaume Nault
2021-01-19 22:30 ` patchwork-bot+netdevbpf [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=161109540897.8518.1356785481446630724.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=gnault@redhat.com \
    --cc=kadlec@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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 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.