All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
	netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com
Subject: Re: [PATCH net 1/2] netfilter: conntrack: Fix data-races around ct mark
Date: Mon, 21 Nov 2022 11:40:15 +0000	[thread overview]
Message-ID: <166903081554.14617.12247850127073077689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118142918.196782-2-pablo@netfilter.org>

Hello:

This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:

On Fri, 18 Nov 2022 15:29:17 +0100 you wrote:
> From: Daniel Xu <dxu@dxuuu.xyz>
> 
> nf_conn:mark can be read from and written to in parallel. Use
> READ_ONCE()/WRITE_ONCE() for reads and writes to prevent unwanted
> compiler optimizations.
> 
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> 
> [...]

Here is the summary with links:
  - [net,1/2] netfilter: conntrack: Fix data-races around ct mark
    https://git.kernel.org/netdev/net/c/52d1aa8b8249
  - [net,2/2] netfilter: nf_tables: do not set up extensions for end interval
    https://git.kernel.org/netdev/net/c/33c7aba0b4ff

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



  reply	other threads:[~2022-11-21 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 14:29 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2022-11-18 14:29 ` [PATCH net 1/2] netfilter: conntrack: Fix data-races around ct mark Pablo Neira Ayuso
2022-11-21 11:40   ` patchwork-bot+netdevbpf [this message]
2022-11-18 14:29 ` [PATCH net 2/2] netfilter: nf_tables: do not set up extensions for end interval Pablo Neira Ayuso

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=166903081554.14617.12247850127073077689.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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.