From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: ralf@linux-mips.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-hams@vger.kernel.org,
netdev@vger.kernel.org, kernelxing@tencent.com
Subject: Re: [PATCH net 00/12] netrom: Fix all the data-races around sysctls
Date: Thu, 07 Mar 2024 10:00:31 +0000 [thread overview]
Message-ID: <170980563143.27682.16929475387592674131.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304082046.64977-1-kerneljasonxing@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 4 Mar 2024 16:20:34 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> As the title said, in this patchset I fix the data-race issues because
> the writer and the reader can manipulate the same value concurrently.
>
> Jason Xing (12):
> netrom: Fix a data-race around sysctl_netrom_default_path_quality
> netrom: Fix a data-race around
> sysctl_netrom_obsolescence_count_initialiser
> netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser
> netrom: Fix a data-race around sysctl_netrom_transport_timeout
> netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries
> netrom: Fix a data-race around
> sysctl_netrom_transport_acknowledge_delay
> netrom: Fix a data-race around sysctl_netrom_transport_busy_delay
> netrom: Fix a data-race around
> sysctl_netrom_transport_requested_window_size
> netrom: Fix a data-race around
> sysctl_netrom_transport_no_activity_timeout
> netrom: Fix a data-race around sysctl_netrom_routing_control
> netrom: Fix a data-race around sysctl_netrom_link_fails_count
> netrom: Fix data-races around sysctl_net_busy_read
>
> [...]
Here is the summary with links:
- [net,01/12] netrom: Fix a data-race around sysctl_netrom_default_path_quality
https://git.kernel.org/netdev/net/c/958d6145a6d9
- [net,02/12] netrom: Fix a data-race around sysctl_netrom_obsolescence_count_initialiser
https://git.kernel.org/netdev/net/c/cfd9f4a740f7
- [net,03/12] netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser
https://git.kernel.org/netdev/net/c/119cae5ea3f9
- [net,04/12] netrom: Fix a data-race around sysctl_netrom_transport_timeout
https://git.kernel.org/netdev/net/c/60a7a152abd4
- [net,05/12] netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries
https://git.kernel.org/netdev/net/c/e799299aafed
- [net,06/12] netrom: Fix a data-race around sysctl_netrom_transport_acknowledge_delay
https://git.kernel.org/netdev/net/c/806f462ba902
- [net,07/12] netrom: Fix a data-race around sysctl_netrom_transport_busy_delay
https://git.kernel.org/netdev/net/c/43547d869943
- [net,08/12] netrom: Fix a data-race around sysctl_netrom_transport_requested_window_size
https://git.kernel.org/netdev/net/c/a2e706841488
- [net,09/12] netrom: Fix a data-race around sysctl_netrom_transport_no_activity_timeout
https://git.kernel.org/netdev/net/c/f99b494b4043
- [net,10/12] netrom: Fix a data-race around sysctl_netrom_routing_control
https://git.kernel.org/netdev/net/c/b5dffcb8f71b
- [net,11/12] netrom: Fix a data-race around sysctl_netrom_link_fails_count
https://git.kernel.org/netdev/net/c/bc76645ebdd0
- [net,12/12] netrom: Fix data-races around sysctl_net_busy_read
https://git.kernel.org/netdev/net/c/d380ce70058a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-07 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 8:20 [PATCH net 00/12] netrom: Fix all the data-races around sysctls Jason Xing
2024-03-04 8:20 ` [PATCH net 01/12] netrom: Fix a data-race around sysctl_netrom_default_path_quality Jason Xing
2024-03-04 8:20 ` [PATCH net 02/12] netrom: Fix a data-race around sysctl_netrom_obsolescence_count_initialiser Jason Xing
2024-03-04 8:20 ` [PATCH net 03/12] netrom: Fix data-races around sysctl_netrom_network_ttl_initialiser Jason Xing
2024-03-04 8:20 ` [PATCH net 04/12] netrom: Fix a data-race around sysctl_netrom_transport_timeout Jason Xing
2024-03-04 8:20 ` [PATCH net 05/12] netrom: Fix a data-race around sysctl_netrom_transport_maximum_tries Jason Xing
2024-03-04 8:20 ` [PATCH net 06/12] netrom: Fix a data-race around sysctl_netrom_transport_acknowledge_delay Jason Xing
2024-03-04 8:20 ` [PATCH net 07/12] netrom: Fix a data-race around sysctl_netrom_transport_busy_delay Jason Xing
2024-03-04 8:20 ` [PATCH net 08/12] netrom: Fix a data-race around sysctl_netrom_transport_requested_window_size Jason Xing
2024-03-04 8:20 ` [PATCH net 09/12] netrom: Fix a data-race around sysctl_netrom_transport_no_activity_timeout Jason Xing
2024-03-04 8:20 ` [PATCH net 10/12] netrom: Fix a data-race around sysctl_netrom_routing_control Jason Xing
2024-03-04 8:20 ` [PATCH net 11/12] netrom: Fix a data-race around sysctl_netrom_link_fails_count Jason Xing
2024-03-04 8:20 ` [PATCH net 12/12] netrom: Fix data-races around sysctl_net_busy_read Jason Xing
2024-03-07 9:36 ` [PATCH net 00/12] netrom: Fix all the data-races around sysctls Paolo Abeni
2024-03-07 9:43 ` Jason Xing
2024-03-07 10:00 ` 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=170980563143.27682.16929475387592674131.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@linux-mips.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).