All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jeroen van Ingen Schenau <jeroen.vaningenschenau@novoserve.com>
Cc: bpf@vger.kernel.org, maximmi@nvidia.com, tariqt@nvidia.com,
	ast@kernel.org, daniel@iogearbox.net, minh.lehoang@novoserve.com
Subject: Re: [PATCH] selftests/bpf: fix erroneous bitmask operation
Date: Fri, 01 Dec 2023 15:20:24 +0000	[thread overview]
Message-ID: <170144402436.18241.3376690555012122181.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231130120353.3084-1-jeroen.vaningenschenau@novoserve.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Thu, 30 Nov 2023 13:03:53 +0100 you wrote:
> xdp_synproxy_kern.c is a BPF program that generates SYN cookies on
> allowed TCP ports and sends SYNACKs to clients, accelerating synproxy
> iptables module.
> 
> Fix the bitmask operation when checking the status of an existing
> conntrack entry within tcp_lookup() function. Do not AND with the bit
> position number, but with the bitmask value to check whether the entry
> found has the IPS_CONFIRMED flag set.
> 
> [...]

Here is the summary with links:
  - selftests/bpf: fix erroneous bitmask operation
    https://git.kernel.org/bpf/bpf-next/c/b6a3451e0847

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



      reply	other threads:[~2023-12-01 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 12:03 [PATCH] selftests/bpf: fix erroneous bitmask operation Jeroen van Ingen Schenau
2023-12-01 15:20 ` 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=170144402436.18241.3376690555012122181.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jeroen.vaningenschenau@novoserve.com \
    --cc=maximmi@nvidia.com \
    --cc=minh.lehoang@novoserve.com \
    --cc=tariqt@nvidia.com \
    /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.