From: Alex Markuze <amarkuze@redhat.com>
To: ceph-devel@vger.kernel.org
Cc: 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,
ebiggers@kernel.org, tytso@mit.edu, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/5] ceph: support subvolume quarantine
Date: Sun, 25 Oct 2026 18:42:40 +0000 [thread overview]
Message-ID: <cover.20261025T182649Z.ca9ae7a18449.git.amarkuze@redhat.com> (raw)
CephFS subvolume quarantine restricts ordinary access while allowing
recovery clients with q/Q MDS auth caps to operate. Add client support
for quarantine notifications and enforce them on cached access paths.
Based on the testing branch of https://github.com/ceph/ceph-client.git,
commit ed0502cb11f8 ("ceph: validate encoded xattr name lengths").
The full base is recorded below. The dcache and fscrypt prerequisites
are included in this five-patch series.
Changes since v5:
- Describe the dcache export as a prerequisite and remove Reported-by
and Closes tags for it.
- Reject foreign, disconnected and unhashed non-root aliases in ancestry
walks while accepting the live, unhashed superblock root.
- Reset quarantine state only when the lost or reconnecting session is
the reporting MDS rank, including when its cap is already absent.
- Check saved authorization's generation even when no inode is marked.
- Check snapshot path access and acquire normal wanted caps after
quarantine authorization.
- Clear detached xattr-buffer ownership after releasing its reference.
- Use synchronous CREATE for new inodes with an LSM security blob,
before async preparation, including before feature negotiation.
- Keep an existing quarantine mark across a zero-error IMPORT while
processing imported caps and negative quarantine errors normally.
- Use the incoming wire cap mask for clear decisions, so PIN-only updates
cannot acquire clear authority from capability bits retained in a merge.
- Update encrypted-symlink and capability comments to match their
interfaces.
Validation: GCC x86_64 builds with fscrypt, ACLs and security enabled
passed W=1 vmlinux/modules for the final tree and the recording patch.
Twenty-six extracted-code quarantine state tests passed, using mocked
kernel context. Live cluster, boot, KASAN/lockdep, LSM policy,
failover, performance and LKMM validation have not been run.
Previous submission:
https://lore.kernel.org/r/cover.1792527529.git.amarkuze@redhat.com/
Alex Markuze (5):
dcache: export d_find_alias_rcu() for modular filesystems
fscrypt: allow filesystems to disable symlink target caching
ceph: add subvolume quarantine wire definitions
ceph: record subvolume quarantine from MDS cap updates
ceph: fail quarantined subvolume access with EACCES
fs/ceph/acl.c | 33 +-
fs/ceph/addr.c | 72 ++-
fs/ceph/caps.c | 323 +++++++++++-
fs/ceph/crypto.c | 1 +
fs/ceph/debugfs.c | 1 +
fs/ceph/dir.c | 54 +-
fs/ceph/file.c | 82 ++-
fs/ceph/inode.c | 956 ++++++++++++++++++++++++++++++++++-
fs/ceph/ioctl.c | 13 +
fs/ceph/mds_client.c | 26 +-
fs/ceph/mds_client.h | 30 +-
fs/ceph/super.c | 4 +
fs/ceph/super.h | 101 +++-
fs/ceph/xattr.c | 60 ++-
fs/crypto/hooks.c | 28 +-
fs/dcache.c | 1 +
include/linux/ceph/ceph_fs.h | 13 +
include/linux/fscrypt.h | 7 +
net/ceph/ceph_common.c | 2 +
19 files changed, 1706 insertions(+), 101 deletions(-)
base-commit: ed0502cb11f84fff29f374238e526ae94d9bdfde
next reply other threads:[~2026-10-25 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 18:42 Alex Markuze [this message]
2026-10-25 18:42 ` [PATCH v6 1/5] dcache: export d_find_alias_rcu() for modular filesystems Alex Markuze
2026-10-25 18:42 ` [PATCH v6 2/5] fscrypt: allow filesystems to disable symlink target caching Alex Markuze
2026-10-25 18:42 ` [PATCH v6 3/5] ceph: add subvolume quarantine wire definitions Alex Markuze
2026-10-25 18:42 ` [PATCH v6 4/5] ceph: record subvolume quarantine from MDS cap updates Alex Markuze
2026-10-25 18:42 ` [PATCH v6 5/5] ceph: fail quarantined subvolume access with EACCES Alex Markuze
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.20261025T182649Z.ca9ae7a18449.git.amarkuze@redhat.com \
--to=amarkuze@redhat.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ebiggers@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
all inboxes | Powered by JetHome®