From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: "Eric W . Biederman" <ebiederm@xmission.com>,
linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
Parav Pandit <parav@nvidia.com>
Subject: Re: [PATCH rdma-next v2 0/9] Check CAP_NET_RAW in right namespace
Date: Tue, 01 Jul 2025 05:22:37 -0400 [thread overview]
Message-ID: <175136175703.403328.5352219442772888831.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1750963874.git.leon@kernel.org>
On Thu, 26 Jun 2025 21:58:03 +0300, Leon Romanovsky wrote:
> Changelog:
> v2:
> * Resend right series
> * Split "RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create"
> * to three small patches. Maybe I should squash them when I'll apply.
> v1: https://lore.kernel.org/all/cover.1750938869.git.leon@kernel.org
> * Moved QP checks to be earlier.
> v0: https://lore.kernel.org/all/cover.1750148509.git.leon@kernel.org
>
> [...]
Applied, thanks!
[1/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create
https://git.kernel.org/rdma/rdma/c/f458ccd2aa2c5a
[2/9] RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create
https://git.kernel.org/rdma/rdma/c/95a89ec304c38f
[3/9] RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create
https://git.kernel.org/rdma/rdma/c/14957e8125e767
[4/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create
https://git.kernel.org/rdma/rdma/c/0498c2d9984ed2
[5/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create
https://git.kernel.org/rdma/rdma/c/c961a341c2c2c2
[6/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create
https://git.kernel.org/rdma/rdma/c/c961a341c2c2c2
[7/9] RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create
https://git.kernel.org/rdma/rdma/c/b5911befe2f910
[8/9] RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify
https://git.kernel.org/rdma/rdma/c/282742fd826ba5
[9/9] RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters
https://git.kernel.org/rdma/rdma/c/d7d403f74f236d
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2025-07-01 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 18:58 [PATCH rdma-next v2 0/9] Check CAP_NET_RAW in right namespace Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 1/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 2/9] RDMA/mlx5: " Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 3/9] RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 4/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 5/9] RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW " Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 6/9] " Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 7/9] RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 8/9] RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify Leon Romanovsky
2025-06-26 18:58 ` [PATCH rdma-next v2 9/9] RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters Leon Romanovsky
2025-07-01 9:22 ` Leon Romanovsky [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=175136175703.403328.5352219442772888831.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=parav@nvidia.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