From: Eric Biggers <ebiggers@kernel.org>
To: Divya Bharathi <divya27392@gmail.com>
Cc: linux-fscrypt@vger.kernel.org, tytso@mit.edu, jaegeuk@kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: fscrypt: document EFAULT return for FS_IOC_SET_ENCRYPTION_POLICY
Date: Fri, 10 Oct 2025 13:39:37 -0700 [thread overview]
Message-ID: <20251010203937.GC2922@quark> (raw)
In-Reply-To: <20251010154753.19216-1-divya27392@gmail.com>
On Fri, Oct 10, 2025 at 09:17:53PM +0530, Divya Bharathi wrote:
> Signed-off-by: Divya Bharathi <divya27392@gmail.com>
> ---
> Documentation/filesystems/fscrypt.rst | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/filesystems/fscrypt.rst b/Documentation/filesystems/fscrypt.rst
> index 4a3e844b7..26cb409e3 100644
> --- a/Documentation/filesystems/fscrypt.rst
> +++ b/Documentation/filesystems/fscrypt.rst
> @@ -729,6 +729,8 @@ FS_IOC_SET_ENCRYPTION_POLICY can fail with the following errors:
> version, mode(s), or flags; or reserved bits were set); or a v1
> encryption policy was specified but the directory has the casefold
> flag enabled (casefolding is incompatible with v1 policies).
> +- ``EFAULT``: an invalid pointer was passed for the encryption policy
> + structure
> - ``ENOKEY``: a v2 encryption policy was specified, but the key with
> the specified ``master_key_identifier`` has not been added, nor does
> the process have the CAP_FOWNER capability in the initial user
> --
> 2.51.0
>
Thanks for the patch!
I think I omitted EFAULT intentionally, since it's always a possibility
for almost any ioctl or syscall that takes a pointer parameter.
If we'd like to explicitly document it, it probably should be documented
for all the ioctls in fscrypt.rst, rather than just
FS_IOC_SET_ENCRYPTION_POLICY.
Also, the list of error codes is alphabetized. EFAULT should go into
the correct position in the list.
- Eric
prev parent reply other threads:[~2025-10-10 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 15:47 [PATCH] docs: fscrypt: document EFAULT return for FS_IOC_SET_ENCRYPTION_POLICY Divya Bharathi
2025-10-10 20:39 ` 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=20251010203937.GC2922@quark \
--to=ebiggers@kernel.org \
--cc=corbet@lwn.net \
--cc=divya27392@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.