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 v5 5/5] ceph: fail quarantined subvolume access with EACCES
Date: Wed, 21 Oct 2026 10:22:38 -0700 [thread overview]
Message-ID: <20261021172238.GD1879@quark> (raw)
In-Reply-To: <345a4e8317cde90293b0d4ee9d8a3edfd229e204.1792527529.git.amarkuze@redhat.com>
On Tue, Oct 20, 2026 at 08:26:50PM +0000, Alex Markuze wrote:
> +/*
> + * fscrypt can cache the decrypted target in ->i_link, allowing the VFS to
> + * bypass this callback. Checking those cache hits needs separate fscrypt
> + * support; this check covers only accesses that reach ->get_link().
> + */
> static const char *ceph_encrypted_get_link(struct dentry *dentry,
> struct inode *inode,
> struct delayed_call *done)
> {
> struct ceph_inode_info *ci = ceph_inode(inode);
> + int err;
>
> if (!dentry)
> return ERR_PTR(-ECHILD);
> + err = ceph_symlink_revalidate(inode);
> + if (err)
> + return ERR_PTR(err);
>
> return fscrypt_get_symlink(inode, ci->i_symlink, i_size_read(inode),
> done);
The function comment seems out of sync with the actual code, as the
actual code disables the symlink target caching.
> case FS_IOC_GET_ENCRYPTION_POLICY:
> ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + ret = ceph_quarantine_revalidate(inode);
> if (ret)
> return ret;
> return fscrypt_ioctl_get_policy(file, (void __user *)arg);
>
> case FS_IOC_GET_ENCRYPTION_POLICY_EX:
> ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + ret = ceph_quarantine_revalidate(inode);
> if (ret)
> return ret;
> return fscrypt_ioctl_get_policy_ex(file, (void __user *)arg);
> @@ -429,6 +439,9 @@ long ceph_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
>
> case FS_IOC_GET_ENCRYPTION_NONCE:
> ret = vet_mds_for_fscrypt(file);
> + if (ret)
> + return ret;
> + ret = ceph_quarantine_revalidate(inode);
> if (ret)
> return ret;
> return fscrypt_ioctl_get_nonce(file, (void __user *)arg);
Can you clarify why FS_IOC_SET_ENCRYPTION_POLICY doesn't need this too?
- Eric
prev parent reply other threads:[~2026-10-21 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 20:26 [PATCH v5 0/5] ceph: support subvolume quarantine Alex Markuze
2026-10-20 20:26 ` [PATCH v5 1/5] dcache: export d_find_alias_rcu() for modular filesystems Alex Markuze
2026-10-21 17:24 ` Eric Biggers
2026-10-20 20:26 ` [PATCH v5 2/5] fscrypt: allow filesystems to disable symlink target caching Alex Markuze
2026-10-20 20:26 ` [PATCH v5 3/5] ceph: add subvolume quarantine wire definitions Alex Markuze
2026-10-20 20:26 ` [PATCH v5 4/5] ceph: record subvolume quarantine from MDS cap updates Alex Markuze
2026-10-20 20:26 ` [PATCH v5 5/5] ceph: fail quarantined subvolume access with EACCES Alex Markuze
2026-10-21 17:22 ` 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=20261021172238.GD1879@quark \
--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
all inboxes | Powered by JetHome®