From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "Eric W . Biederman" <ebiederm@xmission.com>,
linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
Parav Pandit <parav@nvidia.com>
Subject: [PATCH rdma-next v2 0/9] Check CAP_NET_RAW in right namespace
Date: Thu, 26 Jun 2025 21:58:03 +0300 [thread overview]
Message-ID: <cover.1750963874.git.leon@kernel.org> (raw)
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
The following series from Parav clears the mud where against which
namespace the CAP_NET_RAW should be checked.
It is followup of this discussion:
https://lore.kernel.org/all/20250313050832.113030-1-parav@nvidia.com
Thanks
Parav Pandit (9):
RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create
RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create
RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create
RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create
RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create
RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create
RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create
RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify
RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA
counters
drivers/infiniband/core/counters.c | 2 +-
drivers/infiniband/core/device.c | 27 +++++++++++++++++
drivers/infiniband/core/nldev.c | 2 +-
drivers/infiniband/core/rdma_core.c | 29 +++++++++++++++++++
drivers/infiniband/core/uverbs_cmd.c | 10 +++----
drivers/infiniband/core/uverbs_std_types_qp.c | 2 +-
drivers/infiniband/hw/mlx5/devx.c | 2 +-
drivers/infiniband/hw/mlx5/fs.c | 4 +--
include/rdma/ib_verbs.h | 3 ++
9 files changed, 70 insertions(+), 11 deletions(-)
--
2.49.0
next reply other threads:[~2025-06-26 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 18:58 Leon Romanovsky [this message]
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 ` [PATCH rdma-next v2 0/9] Check CAP_NET_RAW in right namespace Leon Romanovsky
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=cover.1750963874.git.leon@kernel.org \
--to=leon@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jgg@nvidia.com \
--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