From: Jens Axboe <axboe@kernel.dk>
To: hch@lst.de, linux-block@vger.kernel.org,
Jingbo Xu <jefflexu@linux.alibaba.com>
Cc: linux-kernel@vger.kernel.org, tianjia.zhang@linux.alibaba.com,
xiang@kernel.org, casey@schaufler-ca.com
Subject: Re: [PATCH v3 0/2] block: fine-granular CAP_SYS_ADMIN for Persistent Reservation ioctl
Date: Tue, 20 Jun 2023 12:51:04 -0600 [thread overview]
Message-ID: <168728706409.3766608.15899699355172012689.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230613084008.93795-1-jefflexu@linux.alibaba.com>
On Tue, 13 Jun 2023 16:40:06 +0800, Jingbo Xu wrote:
> changes since v2:
> - patch 1: disallow reservations on partitions entirely and make it into
> a separate patch (hch)
> - patch 2: rebase to hch's series of converting fmode_t to blk_mode_t
> and execute permission check upon blk_mode_t (hch)
>
> changes since RFC:
> - only allow unprivileged reservations if the file descriptor is open
> for write (Christoph Hellwig)
> - refuse the unprivileged reservations on partitions (Christoph Hellwig)
> (maybe this checking shall also be done when CAP_SYS_ADMIN is set?)
>
> [...]
Applied, thanks!
[1/2] block: disallow Persistent Reservation on partitions
commit: 12629621669b239445727256d1a5dab616b30deb
[2/2] block: fine-granular CAP_SYS_ADMIN for Persistent Reservation
commit: 9a72a02456a839676fe8f220a44ef00951596047
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-06-20 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 8:40 Jingbo Xu
2023-06-13 8:40 ` [PATCH v3 1/2] block: disallow Persistent Reservation on partitions Jingbo Xu
2023-06-13 13:49 ` Christoph Hellwig
2023-06-13 8:40 ` [PATCH v3 2/2] block: fine-granular CAP_SYS_ADMIN for Persistent Reservation Jingbo Xu
2023-06-13 13:49 ` Christoph Hellwig
2023-06-19 7:16 ` [PATCH v3 0/2] block: fine-granular CAP_SYS_ADMIN for Persistent Reservation ioctl Jingbo Xu
2023-06-20 18:51 ` Jens Axboe [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=168728706409.3766608.15899699355172012689.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=casey@schaufler-ca.com \
--cc=hch@lst.de \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tianjia.zhang@linux.alibaba.com \
--cc=xiang@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
all inboxes | Powered by JetHome®