netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	dsahern@kernel.org, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 00/14] ipv6: round of data-races fixes
Date: Fri, 15 Sep 2023 09:40:29 +0000	[thread overview]
Message-ID: <169477082927.23365.2345477309457750514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912160212.3467976-1-edumazet@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Tue, 12 Sep 2023 16:01:58 +0000 you wrote:
> This series is inspired by one related syzbot report.
> 
> Many inet6_sk(sk) fields reads or writes are racy.
> 
> Move 1-bit fields to inet->inet_flags to provide
> atomic safety. inet6_{test|set|clear|assign}_bit() helpers
> could be changed later if we need to make room in inet_flags.
> 
> [...]

Here is the summary with links:
  - [net-next,01/14] ipv6: lockless IPV6_UNICAST_HOPS implementation
    https://git.kernel.org/netdev/net-next/c/b0adfba7ee77
  - [net-next,02/14] ipv6: lockless IPV6_MULTICAST_LOOP implementation
    https://git.kernel.org/netdev/net-next/c/d986f52124e0
  - [net-next,03/14] ipv6: lockless IPV6_MULTICAST_HOPS implementation
    https://git.kernel.org/netdev/net-next/c/2da23eb07c91
  - [net-next,04/14] ipv6: lockless IPV6_MTU implementation
    https://git.kernel.org/netdev/net-next/c/15f926c4457a
  - [net-next,05/14] ipv6: lockless IPV6_MINHOPCOUNT implementation
    https://git.kernel.org/netdev/net-next/c/273784d3c574
  - [net-next,06/14] ipv6: lockless IPV6_RECVERR_RFC4884 implementation
    https://git.kernel.org/netdev/net-next/c/dcae74622c05
  - [net-next,07/14] ipv6: lockless IPV6_MULTICAST_ALL implementation
    https://git.kernel.org/netdev/net-next/c/6559c0ff3bc2
  - [net-next,08/14] ipv6: lockless IPV6_AUTOFLOWLABEL implementation
    https://git.kernel.org/netdev/net-next/c/5121516b0c47
  - [net-next,09/14] ipv6: lockless IPV6_DONTFRAG implementation
    https://git.kernel.org/netdev/net-next/c/1086ca7cce29
  - [net-next,10/14] ipv6: lockless IPV6_RECVERR implemetation
    https://git.kernel.org/netdev/net-next/c/3fa29971c695
  - [net-next,11/14] ipv6: move np->repflow to atomic flags
    https://git.kernel.org/netdev/net-next/c/3cccda8db2cf
  - [net-next,12/14] ipv6: lockless IPV6_ROUTER_ALERT_ISOLATE implementation
    https://git.kernel.org/netdev/net-next/c/83cd5eb654b3
  - [net-next,13/14] ipv6: lockless IPV6_MTU_DISCOVER implementation
    https://git.kernel.org/netdev/net-next/c/6b724bc4300b
  - [net-next,14/14] ipv6: lockless IPV6_FLOWINFO_SEND implementation
    https://git.kernel.org/netdev/net-next/c/859f8b265fc2

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



      parent reply	other threads:[~2023-09-15  9:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 16:01 [PATCH net-next 00/14] ipv6: round of data-races fixes Eric Dumazet
2023-09-12 16:01 ` [PATCH net-next 01/14] ipv6: lockless IPV6_UNICAST_HOPS implementation Eric Dumazet
2023-09-14 14:51   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 02/14] ipv6: lockless IPV6_MULTICAST_LOOP implementation Eric Dumazet
2023-09-14 14:54   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 03/14] ipv6: lockless IPV6_MULTICAST_HOPS implementation Eric Dumazet
2023-09-14 14:55   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 04/14] ipv6: lockless IPV6_MTU implementation Eric Dumazet
2023-09-14 14:58   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 05/14] ipv6: lockless IPV6_MINHOPCOUNT implementation Eric Dumazet
2023-09-14 15:01   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 06/14] ipv6: lockless IPV6_RECVERR_RFC4884 implementation Eric Dumazet
2023-09-14 15:02   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 07/14] ipv6: lockless IPV6_MULTICAST_ALL implementation Eric Dumazet
2023-09-14 15:03   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 08/14] ipv6: lockless IPV6_AUTOFLOWLABEL implementation Eric Dumazet
2023-09-14 15:04   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 09/14] ipv6: lockless IPV6_DONTFRAG implementation Eric Dumazet
2023-09-14 15:05   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 10/14] ipv6: lockless IPV6_RECVERR implemetation Eric Dumazet
2023-09-14 15:06   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 11/14] ipv6: move np->repflow to atomic flags Eric Dumazet
2023-09-14 15:07   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 12/14] ipv6: lockless IPV6_ROUTER_ALERT_ISOLATE implementation Eric Dumazet
2023-09-14 15:08   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 13/14] ipv6: lockless IPV6_MTU_DISCOVER implementation Eric Dumazet
2023-09-14 15:10   ` David Ahern
2023-09-12 16:02 ` [PATCH net-next 14/14] ipv6: lockless IPV6_FLOWINFO_SEND implementation Eric Dumazet
2023-09-14 15:11   ` David Ahern
2023-09-14 10:25 ` [PATCH net-next 00/14] ipv6: round of data-races fixes Simon Horman
2023-09-15  9:40 ` 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=169477082927.23365.2345477309457750514.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).