From: Richard Weinberger <richard-/L3Ra7n9ekc@public.gmane.org>
To: Eric Biggers <ebiggers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
fstests-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
Jaegeuk Kim <jaegeuk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
David Gstir <david-S6VGOU4v5edDinCvNWH78Q@public.gmane.org>,
Michael Halcrow
<mhalcrow-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2 4/5] generic: test encrypted file access
Date: Tue, 29 Nov 2016 21:52:10 +0100 [thread overview]
Message-ID: <efa324fb-6d0b-aad0-1916-cdf12f0072c0@nod.at> (raw)
In-Reply-To: <1480371402-12204-5-git-send-email-ebiggers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Eric,
On 28.11.2016 23:16, Eric Biggers wrote:
> +# Also, there are some inconsistencies in which error codes are returned on
> +# different kernel versions and filesystems when trying to create a file or
> +# subdirectory without access to the parent directory's encryption key. For now
> +# we just accept multiple error codes.
This is something I wanted to ask about some time ago but forgot.
Can we please agree on a clear set of fscrypt related error codes
and document them in the Linux man pages?
Thanks,
//richard
next parent reply other threads:[~2016-11-29 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1480371402-12204-1-git-send-email-ebiggers@google.com>
[not found] ` <1480371402-12204-5-git-send-email-ebiggers@google.com>
[not found] ` <1480371402-12204-5-git-send-email-ebiggers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-11-29 20:52 ` Richard Weinberger [this message]
2016-12-01 0:30 ` [PATCH v2 4/5] generic: test encrypted file access Eric Biggers
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=efa324fb-6d0b-aad0-1916-cdf12f0072c0@nod.at \
--to=richard-/l3ra7n9ekc@public.gmane.org \
--cc=david-S6VGOU4v5edDinCvNWH78Q@public.gmane.org \
--cc=ebiggers-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=fstests-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jaegeuk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mhalcrow-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).