Re: [PATCH net-next 00/14] ipv6: round of data-races fixes

[Simon Horman <horms@kernel.org>]

On Tue, Sep 12, 2023 at 04:01:58PM +0000, Eric Dumazet 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.
> 
> Also add missing READ_ONCE()/WRITE_ONCE() when
> lockless readers need access to specific fields.
> 
> np->srcprefs will be handled separately to avoid merge conflicts
> because a prior patch was posted for net tree.
> 
> Eric Dumazet (14):
>   ipv6: lockless IPV6_UNICAST_HOPS implementation
>   ipv6: lockless IPV6_MULTICAST_LOOP implementation
>   ipv6: lockless IPV6_MULTICAST_HOPS implementation
>   ipv6: lockless IPV6_MTU implementation
>   ipv6: lockless IPV6_MINHOPCOUNT implementation
>   ipv6: lockless IPV6_RECVERR_RFC4884 implementation
>   ipv6: lockless IPV6_MULTICAST_ALL implementation
>   ipv6: lockless IPV6_AUTOFLOWLABEL implementation
>   ipv6: lockless IPV6_DONTFRAG implementation
>   ipv6: lockless IPV6_RECVERR implemetation
>   ipv6: move np->repflow to atomic flags
>   ipv6: lockless IPV6_ROUTER_ALERT_ISOLATE implementation
>   ipv6: lockless IPV6_MTU_DISCOVER implementation
>   ipv6: lockless IPV6_FLOWINFO_SEND implementation

For series,

Reviewed-by: Simon Horman <horms@kernel.org>