From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, davem@davemloft.net,
kuba@kernel.org, horms@kernel.org, stefan.wiehler@nokia.com,
dsahern@kernel.org
Subject: Re: [PATCH v2 net 0/3] net: fix mcast RCU splats
Date: Thu, 28 Nov 2024 09:30:31 +0000 [thread overview]
Message-ID: <173278623126.1676038.10017365544015703549.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1732289799.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 24 Nov 2024 16:40:55 +0100 you wrote:
> This series addresses the RCU splat triggered by the forwarding
> mroute tests.
>
> The first patch does not address any specific issue, but makes the
> following ones more clear. Patch 2 and 3 address the issue for ipv6 and
> ipv4 respectively.
>
> [...]
Here is the summary with links:
- [v2,net,1/3] ipmr: add debug check for mr table cleanup
https://git.kernel.org/netdev/net/c/11b6e701bce9
- [v2,net,2/3] ip6mr: fix tables suspicious RCU usage
https://git.kernel.org/netdev/net/c/f1553c9894b4
- [v2,net,3/3] ipmr: fix tables suspicious RCU usage
https://git.kernel.org/netdev/net/c/fc9c273d6daa
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-11-28 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 15:40 [PATCH v2 net 0/3] net: fix mcast RCU splats Paolo Abeni
2024-11-24 15:40 ` [PATCH v2 net 1/3] ipmr: add debug check for mr table cleanup Paolo Abeni
2024-11-26 15:34 ` David Ahern
2024-11-24 15:40 ` [PATCH v2 net 2/3] ip6mr: fix tables suspicious RCU usage Paolo Abeni
2024-11-26 15:39 ` David Ahern
2024-11-24 15:40 ` [PATCH v2 net 3/3] ipmr: " Paolo Abeni
2024-11-26 15:40 ` David Ahern
2024-11-28 9:30 ` 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=173278623126.1676038.10017365544015703549.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan.wiehler@nokia.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).