From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, martineau@kernel.org, geliang@kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, donald.hunter@gmail.com,
dcaratti@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net 0/2] mptcp: pm: fix wrong perm and sock kfree
Date: Wed, 06 Nov 2024 02:20:34 +0000 [thread overview]
Message-ID: <173085963449.771890.15377735396681814695.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241104-net-mptcp-misc-6-12-v1-0-c13f2ff1656f@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 04 Nov 2024 13:31:40 +0100 you wrote:
> Two small fixes related to the MPTCP path-manager:
>
> - Patch 1: remove an accidental restriction to admin users to list MPTCP
> endpoints. A regression from v6.7.
>
> - Patch 2: correctly use sock_kfree_s() instead of kfree() in the
> userspace PM. A fix for another fix introduced in v6.4 and
> backportable up to v5.19.
>
> [...]
Here is the summary with links:
- [net,1/2] mptcp: no admin perm to list endpoints
https://git.kernel.org/netdev/net/c/cfbbd4859882
- [net,2/2] mptcp: use sock_kfree_s instead of kfree
https://git.kernel.org/netdev/net/c/99635c91fb8b
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-06 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 12:31 [PATCH net 0/2] mptcp: pm: fix wrong perm and sock kfree Matthieu Baerts (NGI0)
2024-11-04 12:31 ` [PATCH net 1/2] mptcp: no admin perm to list endpoints Matthieu Baerts (NGI0)
2024-11-04 12:31 ` [PATCH net 2/2] mptcp: use sock_kfree_s instead of kfree Matthieu Baerts (NGI0)
2024-11-06 2:20 ` 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=173085963449.771890.15377735396681814695.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.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