From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 00/19] ipmr: get rid of rwlocks
Date: Fri, 24 Jun 2022 10:50:20 +0000 [thread overview]
Message-ID: <165606782016.15655.1274087026188806431.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220623043449.1217288-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 23 Jun 2022 04:34:30 +0000 you wrote:
> We need to get rid of rwlocks in networking stacks,
> if read_lock() is (ab)used from softirq context.
>
> As discussed recently [1], rwlock are unfair by design in this case,
> and writers can starve and trigger soft lockups.
>
> This series convert ipmr code (both IPv4 and IPv6 families)
> to RCU and spinlocks.
>
> [...]
Here is the summary with links:
- [v2,net-next,01/19] ip6mr: do not get a device reference in pim6_rcv()
https://git.kernel.org/netdev/net-next/c/0a24c43f54b2
- [v2,net-next,02/19] ipmr: add rcu protection over (struct vif_device)->dev
https://git.kernel.org/netdev/net-next/c/ebc3197963fc
- [v2,net-next,03/19] ipmr: change igmpmsg_netlink_event() prototype
https://git.kernel.org/netdev/net-next/c/0b490b51d226
- [v2,net-next,04/19] ipmr: ipmr_cache_report() changes
https://git.kernel.org/netdev/net-next/c/646679881a02
- [v2,net-next,05/19] ipmr: do not acquire mrt_lock in __pim_rcv()
https://git.kernel.org/netdev/net-next/c/121fefc669bf
- [v2,net-next,06/19] ipmr: do not acquire mrt_lock in ioctl(SIOCGETVIFCNT)
https://git.kernel.org/netdev/net-next/c/559260fd9d9a
- [v2,net-next,07/19] ipmr: do not acquire mrt_lock before calling ipmr_cache_unresolved()
https://git.kernel.org/netdev/net-next/c/9094db4b8004
- [v2,net-next,08/19] ipmr: do not acquire mrt_lock while calling ip_mr_forward()
https://git.kernel.org/netdev/net-next/c/4eadb88244d1
- [v2,net-next,09/19] ipmr: do not acquire mrt_lock in ipmr_get_route()
https://git.kernel.org/netdev/net-next/c/e4cd9868e8ec
- [v2,net-next,10/19] ip6mr: ip6mr_cache_report() changes
https://git.kernel.org/netdev/net-next/c/3493a5b730e5
- [v2,net-next,11/19] ip6mr: do not acquire mrt_lock in pim6_rcv()
https://git.kernel.org/netdev/net-next/c/6d08658736fc
- [v2,net-next,12/19] ip6mr: do not acquire mrt_lock in ioctl(SIOCGETMIFCNT_IN6)
https://git.kernel.org/netdev/net-next/c/638cf4a24a09
- [v2,net-next,13/19] ip6mr: do not acquire mrt_lock before calling ip6mr_cache_unresolved
https://git.kernel.org/netdev/net-next/c/db9eb7c8ae34
- [v2,net-next,14/19] ip6mr: do not acquire mrt_lock while calling ip6_mr_forward()
https://git.kernel.org/netdev/net-next/c/9b1c21d898fd
- [v2,net-next,15/19] ip6mr: switch ip6mr_get_route() to rcu_read_lock()
https://git.kernel.org/netdev/net-next/c/6fa40a290219
- [v2,net-next,16/19] ipmr: adopt rcu_read_lock() in mr_dump()
https://git.kernel.org/netdev/net-next/c/194366b28b83
- [v2,net-next,17/19] ipmr: convert /proc handlers to rcu_read_lock()
https://git.kernel.org/netdev/net-next/c/b96ef16d2f83
- [v2,net-next,18/19] ipmr: convert mrt_lock to a spinlock
https://git.kernel.org/netdev/net-next/c/3f55211ecf6a
- [v2,net-next,19/19] ip6mr: convert mrt_lock to a spinlock
https://git.kernel.org/netdev/net-next/c/a96f7a6a60b3
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:[~2022-06-24 10:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 4:34 [PATCH v2 net-next 00/19] ipmr: get rid of rwlocks Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 01/19] ip6mr: do not get a device reference in pim6_rcv() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 02/19] ipmr: add rcu protection over (struct vif_device)->dev Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 03/19] ipmr: change igmpmsg_netlink_event() prototype Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 04/19] ipmr: ipmr_cache_report() changes Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 05/19] ipmr: do not acquire mrt_lock in __pim_rcv() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 06/19] ipmr: do not acquire mrt_lock in ioctl(SIOCGETVIFCNT) Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 07/19] ipmr: do not acquire mrt_lock before calling ipmr_cache_unresolved() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 08/19] ipmr: do not acquire mrt_lock while calling ip_mr_forward() Eric Dumazet
2022-07-22 19:34 ` Vladimir Oltean
2022-07-22 20:37 ` Eric Dumazet
2022-07-22 21:10 ` Vladimir Oltean
2022-07-22 21:15 ` Vladimir Oltean
2022-06-23 4:34 ` [PATCH v2 net-next 09/19] ipmr: do not acquire mrt_lock in ipmr_get_route() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 10/19] ip6mr: ip6mr_cache_report() changes Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 11/19] ip6mr: do not acquire mrt_lock in pim6_rcv() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 12/19] ip6mr: do not acquire mrt_lock in ioctl(SIOCGETMIFCNT_IN6) Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 13/19] ip6mr: do not acquire mrt_lock before calling ip6mr_cache_unresolved Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 14/19] ip6mr: do not acquire mrt_lock while calling ip6_mr_forward() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 15/19] ip6mr: switch ip6mr_get_route() to rcu_read_lock() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 16/19] ipmr: adopt rcu_read_lock() in mr_dump() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 17/19] ipmr: convert /proc handlers to rcu_read_lock() Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 18/19] ipmr: convert mrt_lock to a spinlock Eric Dumazet
2022-06-23 4:34 ` [PATCH v2 net-next 19/19] ip6mr: " Eric Dumazet
2022-06-24 10:50 ` 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=165606782016.15655.1274087026188806431.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--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 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.