From: Eric Biggers <ebiggers@kernel.org>
To: Alex Markuze <amarkuze@redhat.com>
Cc: ceph-devel@vger.kernel.org, idryomov@gmail.com,
xiubo.li@clyso.com, slava@dubeyko.com, viro@zeniv.linux.org.uk,
brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-fscrypt@vger.kernel.org, tytso@mit.edu, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] ceph: support subvolume quarantine
Date: Tue, 20 Oct 2026 16:05:37 +0000 [thread overview]
Message-ID: <20261020160537.GD699485@google.com> (raw)
In-Reply-To: <cover.1792498351.git.amarkuze@redhat.com>
On Tue, Oct 20, 2026 at 12:52:32PM +0000, Alex Markuze wrote:
> CephFS subvolume quarantine isolates a subvolume while allowing recovery
> clients with q/Q MDS auth caps to access it. Advertise support only after
> cached data and metadata access paths can enforce quarantine.
No base-commit given, and this fails to apply to current mainline,
current linux-next, and also to the current default branch of
https://github.com/ceph/ceph-client.git which MAINTAINERS lists for
fs/ceph/. So it isn't possible to review this.
Note that Sashiko was unable to apply it too, so no reviews from Sashiko
are available either.
It's getting to the point where I should just immediately delete all
patches that don't have a base-commit. It's a waste of time to even
bother trying to look at them.
- Eric
prev parent reply other threads:[~2026-10-20 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 12:52 [PATCH v4 0/5] ceph: support subvolume quarantine Alex Markuze
2026-10-20 12:52 ` [PATCH v4 1/5] dcache: export d_find_alias_rcu() for modular filesystems Alex Markuze
2026-10-20 12:52 ` [PATCH v4 2/5] fscrypt: allow filesystems to disable symlink target caching Alex Markuze
2026-10-20 12:52 ` [PATCH v4 3/5] ceph: add subvolume quarantine wire definitions Alex Markuze
2026-10-20 12:52 ` [PATCH v4 4/5] ceph: record subvolume quarantine from MDS cap updates Alex Markuze
2026-10-20 12:52 ` [PATCH v4 5/5] ceph: fail quarantined subvolume access with EACCES Alex Markuze
2026-10-20 16:05 ` Eric Biggers [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=20261020160537.GD699485@google.com \
--to=ebiggers@kernel.org \
--cc=amarkuze@redhat.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xiubo.li@clyso.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