All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "Eric W . Biederman" <ebiederm@xmission.com>,
	linux-rdma@vger.kernel.org, Parav Pandit <parav@nvidia.com>,
	Mark Bloch <mbloch@nvidia.com>
Subject: Re: [PATCH rdma-next v1 0/7] Check CAP_NET_RAW in right namespace
Date: Thu, 26 Jun 2025 15:20:15 +0300	[thread overview]
Message-ID: <20250626122015.GJ17401@unreal> (raw)
In-Reply-To: <cover.1750938869.git.leon@kernel.org>

On Thu, Jun 26, 2025 at 03:05:51PM +0300, Leon Romanovsky wrote:
> Changelog:
> v1: 
>  * Moved QP checks to be earlier. 
> v0: https://lore.kernel.org/all/cover.1750148509.git.leon@kernel.org

Please discard this version, it is wrong one.

Thanks

      parent reply	other threads:[~2025-06-26 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 12:05 [PATCH rdma-next v1 0/7] Check CAP_NET_RAW in right namespace Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 1/7] RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 2/7] RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 3/7] RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 4/7] RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 5/7] RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 6/7] RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters Leon Romanovsky
2025-06-26 12:05 ` [PATCH rdma-next v1 7/7] RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify Leon Romanovsky
2025-06-26 12:20 ` 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=20250626122015.GJ17401@unreal \
    --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 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.