From: Michael Halcrow <mhalcrow@google.com> To: Eric Biggers <ebiggers3@gmail.com> Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-mtd@lists.infradead.org, linux-api@vger.kernel.org, keyrings@vger.kernel.org, "Theodore Y . Ts'o" <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>, Gwendal Grignou <gwendal@chromium.org>, Ryo Hashimoto <hashimoto@chromium.org>, Sarthak Kukreti <sarthakkukreti@chromium.org>, Nick Desaulniers <ndesaulniers@google.com>, Eric Biggers <ebiggers@google.com> Subject: Re: [RFC PATCH 01/25] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h> Date: Fri, 27 Oct 2017 11:01:41 -0700 [thread overview] Message-ID: <20171027180141.GA10611@google.com> (raw) In-Reply-To: <20171023214058.128121-2-ebiggers3@gmail.com> On Mon, Oct 23, 2017 at 02:40:34PM -0700, Eric Biggers wrote: > From: Eric Biggers <ebiggers@google.com> > > There are going to be more filesystem encryption definitions added, and > we don't want to use a disproportionate amount of space in <linux/fs.h> > for filesystem encryption stuff. So move the fscrypt definitions to a > new header <linux/fscrypt.h>. > > For compatibility with existing userspace programs which may be > including <linux/fs.h>, <linux/fs.h> still includes the new header. > (It's debatable whether we really need this, though; the filesystem > encryption API is new enough that most if not all programs that are > using it have to declare it themselves anyway.) > > Signed-off-by: Eric Biggers <ebiggers@google.com> Reviewed-by: Michael Halcrow <mhalcrow@google.com> > --- > include/linux/fscrypt.h | 2 +- > include/uapi/linux/fs.h | 50 +++-------------------------------------- > include/uapi/linux/fscrypt.h | 53 ++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 57 insertions(+), 48 deletions(-) > create mode 100644 include/uapi/linux/fscrypt.h > > diff --git a/include/linux/fscrypt.h b/include/linux/fscrypt.h > index 53437bfdfcbc..f7aa7d62e235 100644 > --- a/include/linux/fscrypt.h > +++ b/include/linux/fscrypt.h > @@ -19,7 +19,7 @@ > #include <linux/bio.h> > #include <linux/dcache.h> > #include <crypto/skcipher.h> > -#include <uapi/linux/fs.h> > +#include <uapi/linux/fscrypt.h> > > #define FS_CRYPTO_BLOCK_SIZE 16 > > diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h > index 56235dddea7d..6ecd3ee9960c 100644 > --- a/include/uapi/linux/fs.h > +++ b/include/uapi/linux/fs.h > @@ -12,6 +12,9 @@ > #include <linux/limits.h> > #include <linux/ioctl.h> > #include <linux/types.h> > +#ifndef __KERNEL__ > +#include <linux/fscrypt.h> > +#endif > > /* > * It's silly to have NR_OPEN bigger than NR_FILE, but you can change > @@ -253,53 +256,6 @@ struct fsxattr { > #define FS_IOC_FSGETXATTR _IOR ('X', 31, struct fsxattr) > #define FS_IOC_FSSETXATTR _IOW ('X', 32, struct fsxattr) > > -/* > - * File system encryption support > - */ > -/* Policy provided via an ioctl on the topmost directory */ > -#define FS_KEY_DESCRIPTOR_SIZE 8 > - > -#define FS_POLICY_FLAGS_PAD_4 0x00 > -#define FS_POLICY_FLAGS_PAD_8 0x01 > -#define FS_POLICY_FLAGS_PAD_16 0x02 > -#define FS_POLICY_FLAGS_PAD_32 0x03 > -#define FS_POLICY_FLAGS_PAD_MASK 0x03 > -#define FS_POLICY_FLAGS_VALID 0x03 > - > -/* Encryption algorithms */ > -#define FS_ENCRYPTION_MODE_INVALID 0 > -#define FS_ENCRYPTION_MODE_AES_256_XTS 1 > -#define FS_ENCRYPTION_MODE_AES_256_GCM 2 > -#define FS_ENCRYPTION_MODE_AES_256_CBC 3 > -#define FS_ENCRYPTION_MODE_AES_256_CTS 4 > -#define FS_ENCRYPTION_MODE_AES_128_CBC 5 > -#define FS_ENCRYPTION_MODE_AES_128_CTS 6 > - > -struct fscrypt_policy { > - __u8 version; > - __u8 contents_encryption_mode; > - __u8 filenames_encryption_mode; > - __u8 flags; > - __u8 master_key_descriptor[FS_KEY_DESCRIPTOR_SIZE]; > -}; > - > -#define FS_IOC_SET_ENCRYPTION_POLICY _IOR('f', 19, struct fscrypt_policy) > -#define FS_IOC_GET_ENCRYPTION_PWSALT _IOW('f', 20, __u8[16]) > -#define FS_IOC_GET_ENCRYPTION_POLICY _IOW('f', 21, struct fscrypt_policy) > - > -/* Parameters for passing an encryption key into the kernel keyring */ > -#define FS_KEY_DESC_PREFIX "fscrypt:" > -#define FS_KEY_DESC_PREFIX_SIZE 8 > - > -/* Structure that userspace passes to the kernel keyring */ > -#define FS_MAX_KEY_SIZE 64 > - > -struct fscrypt_key { > - __u32 mode; > - __u8 raw[FS_MAX_KEY_SIZE]; > - __u32 size; > -}; > - > /* > * Inode flags (FS_IOC_GETFLAGS / FS_IOC_SETFLAGS) > * > diff --git a/include/uapi/linux/fscrypt.h b/include/uapi/linux/fscrypt.h > new file mode 100644 > index 000000000000..c09209fc42ea > --- /dev/null > +++ b/include/uapi/linux/fscrypt.h > @@ -0,0 +1,53 @@ > +#ifndef _UAPI_LINUX_FSCRYPT_H > +#define _UAPI_LINUX_FSCRYPT_H > + > +#include <linux/types.h> > + > +/* > + * File system encryption support > + */ > +/* Policy provided via an ioctl on the topmost directory */ > +#define FS_KEY_DESCRIPTOR_SIZE 8 > + > +#define FS_POLICY_FLAGS_PAD_4 0x00 > +#define FS_POLICY_FLAGS_PAD_8 0x01 > +#define FS_POLICY_FLAGS_PAD_16 0x02 > +#define FS_POLICY_FLAGS_PAD_32 0x03 > +#define FS_POLICY_FLAGS_PAD_MASK 0x03 > +#define FS_POLICY_FLAGS_VALID 0x03 > + > +/* Encryption algorithms */ > +#define FS_ENCRYPTION_MODE_INVALID 0 > +#define FS_ENCRYPTION_MODE_AES_256_XTS 1 > +#define FS_ENCRYPTION_MODE_AES_256_GCM 2 > +#define FS_ENCRYPTION_MODE_AES_256_CBC 3 > +#define FS_ENCRYPTION_MODE_AES_256_CTS 4 > +#define FS_ENCRYPTION_MODE_AES_128_CBC 5 > +#define FS_ENCRYPTION_MODE_AES_128_CTS 6 > + > +struct fscrypt_policy { > + __u8 version; > + __u8 contents_encryption_mode; > + __u8 filenames_encryption_mode; > + __u8 flags; > + __u8 master_key_descriptor[FS_KEY_DESCRIPTOR_SIZE]; > +}; > + > +#define FS_IOC_SET_ENCRYPTION_POLICY _IOR('f', 19, struct fscrypt_policy) > +#define FS_IOC_GET_ENCRYPTION_PWSALT _IOW('f', 20, __u8[16]) > +#define FS_IOC_GET_ENCRYPTION_POLICY _IOW('f', 21, struct fscrypt_policy) > + > +/* Parameters for passing an encryption key into the kernel keyring */ > +#define FS_KEY_DESC_PREFIX "fscrypt:" > +#define FS_KEY_DESC_PREFIX_SIZE 8 > + > +/* Structure that userspace passes to the kernel keyring */ > +#define FS_MAX_KEY_SIZE 64 > + > +struct fscrypt_key { > + __u32 mode; > + __u8 raw[FS_MAX_KEY_SIZE]; > + __u32 size; > +}; > + > +#endif /* _UAPI_LINUX_FSCRYPT_H */ > -- > 2.15.0.rc0.271.g36b669edcc-goog >
WARNING: multiple messages have this Message-ID (diff)
From: Michael Halcrow <mhalcrow@google.com> To: Eric Biggers <ebiggers3@gmail.com> Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-mtd@lists.infradead.org, linux-api@vger.kernel.org, keyrings@vger.kernel.org, "Theodore Y . Ts'o" <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>, Gwendal Grignou <gwendal@chromium.org>, Ryo Hashimoto <hashimoto@chromium.org>, Sarthak Kukreti <sarthakkukreti@chromium.org>, Nick Desaulniers <ndesaulniers@google.com>, Eric Biggers <ebiggers@google.com> Subject: Re: [RFC PATCH 01/25] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h> Date: Fri, 27 Oct 2017 18:01:41 +0000 [thread overview] Message-ID: <20171027180141.GA10611@google.com> (raw) In-Reply-To: <20171023214058.128121-2-ebiggers3@gmail.com> On Mon, Oct 23, 2017 at 02:40:34PM -0700, Eric Biggers wrote: > From: Eric Biggers <ebiggers@google.com> > > There are going to be more filesystem encryption definitions added, and > we don't want to use a disproportionate amount of space in <linux/fs.h> > for filesystem encryption stuff. So move the fscrypt definitions to a > new header <linux/fscrypt.h>. > > For compatibility with existing userspace programs which may be > including <linux/fs.h>, <linux/fs.h> still includes the new header. > (It's debatable whether we really need this, though; the filesystem > encryption API is new enough that most if not all programs that are > using it have to declare it themselves anyway.) > > Signed-off-by: Eric Biggers <ebiggers@google.com> Reviewed-by: Michael Halcrow <mhalcrow@google.com> > --- > include/linux/fscrypt.h | 2 +- > include/uapi/linux/fs.h | 50 +++-------------------------------------- > include/uapi/linux/fscrypt.h | 53 ++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 57 insertions(+), 48 deletions(-) > create mode 100644 include/uapi/linux/fscrypt.h > > diff --git a/include/linux/fscrypt.h b/include/linux/fscrypt.h > index 53437bfdfcbc..f7aa7d62e235 100644 > --- a/include/linux/fscrypt.h > +++ b/include/linux/fscrypt.h > @@ -19,7 +19,7 @@ > #include <linux/bio.h> > #include <linux/dcache.h> > #include <crypto/skcipher.h> > -#include <uapi/linux/fs.h> > +#include <uapi/linux/fscrypt.h> > > #define FS_CRYPTO_BLOCK_SIZE 16 > > diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h > index 56235dddea7d..6ecd3ee9960c 100644 > --- a/include/uapi/linux/fs.h > +++ b/include/uapi/linux/fs.h > @@ -12,6 +12,9 @@ > #include <linux/limits.h> > #include <linux/ioctl.h> > #include <linux/types.h> > +#ifndef __KERNEL__ > +#include <linux/fscrypt.h> > +#endif > > /* > * It's silly to have NR_OPEN bigger than NR_FILE, but you can change > @@ -253,53 +256,6 @@ struct fsxattr { > #define FS_IOC_FSGETXATTR _IOR ('X', 31, struct fsxattr) > #define FS_IOC_FSSETXATTR _IOW ('X', 32, struct fsxattr) > > -/* > - * File system encryption support > - */ > -/* Policy provided via an ioctl on the topmost directory */ > -#define FS_KEY_DESCRIPTOR_SIZE 8 > - > -#define FS_POLICY_FLAGS_PAD_4 0x00 > -#define FS_POLICY_FLAGS_PAD_8 0x01 > -#define FS_POLICY_FLAGS_PAD_16 0x02 > -#define FS_POLICY_FLAGS_PAD_32 0x03 > -#define FS_POLICY_FLAGS_PAD_MASK 0x03 > -#define FS_POLICY_FLAGS_VALID 0x03 > - > -/* Encryption algorithms */ > -#define FS_ENCRYPTION_MODE_INVALID 0 > -#define FS_ENCRYPTION_MODE_AES_256_XTS 1 > -#define FS_ENCRYPTION_MODE_AES_256_GCM 2 > -#define FS_ENCRYPTION_MODE_AES_256_CBC 3 > -#define FS_ENCRYPTION_MODE_AES_256_CTS 4 > -#define FS_ENCRYPTION_MODE_AES_128_CBC 5 > -#define FS_ENCRYPTION_MODE_AES_128_CTS 6 > - > -struct fscrypt_policy { > - __u8 version; > - __u8 contents_encryption_mode; > - __u8 filenames_encryption_mode; > - __u8 flags; > - __u8 master_key_descriptor[FS_KEY_DESCRIPTOR_SIZE]; > -}; > - > -#define FS_IOC_SET_ENCRYPTION_POLICY _IOR('f', 19, struct fscrypt_policy) > -#define FS_IOC_GET_ENCRYPTION_PWSALT _IOW('f', 20, __u8[16]) > -#define FS_IOC_GET_ENCRYPTION_POLICY _IOW('f', 21, struct fscrypt_policy) > - > -/* Parameters for passing an encryption key into the kernel keyring */ > -#define FS_KEY_DESC_PREFIX "fscrypt:" > -#define FS_KEY_DESC_PREFIX_SIZE 8 > - > -/* Structure that userspace passes to the kernel keyring */ > -#define FS_MAX_KEY_SIZE 64 > - > -struct fscrypt_key { > - __u32 mode; > - __u8 raw[FS_MAX_KEY_SIZE]; > - __u32 size; > -}; > - > /* > * Inode flags (FS_IOC_GETFLAGS / FS_IOC_SETFLAGS) > * > diff --git a/include/uapi/linux/fscrypt.h b/include/uapi/linux/fscrypt.h > new file mode 100644 > index 000000000000..c09209fc42ea > --- /dev/null > +++ b/include/uapi/linux/fscrypt.h > @@ -0,0 +1,53 @@ > +#ifndef _UAPI_LINUX_FSCRYPT_H > +#define _UAPI_LINUX_FSCRYPT_H > + > +#include <linux/types.h> > + > +/* > + * File system encryption support > + */ > +/* Policy provided via an ioctl on the topmost directory */ > +#define FS_KEY_DESCRIPTOR_SIZE 8 > + > +#define FS_POLICY_FLAGS_PAD_4 0x00 > +#define FS_POLICY_FLAGS_PAD_8 0x01 > +#define FS_POLICY_FLAGS_PAD_16 0x02 > +#define FS_POLICY_FLAGS_PAD_32 0x03 > +#define FS_POLICY_FLAGS_PAD_MASK 0x03 > +#define FS_POLICY_FLAGS_VALID 0x03 > + > +/* Encryption algorithms */ > +#define FS_ENCRYPTION_MODE_INVALID 0 > +#define FS_ENCRYPTION_MODE_AES_256_XTS 1 > +#define FS_ENCRYPTION_MODE_AES_256_GCM 2 > +#define FS_ENCRYPTION_MODE_AES_256_CBC 3 > +#define FS_ENCRYPTION_MODE_AES_256_CTS 4 > +#define FS_ENCRYPTION_MODE_AES_128_CBC 5 > +#define FS_ENCRYPTION_MODE_AES_128_CTS 6 > + > +struct fscrypt_policy { > + __u8 version; > + __u8 contents_encryption_mode; > + __u8 filenames_encryption_mode; > + __u8 flags; > + __u8 master_key_descriptor[FS_KEY_DESCRIPTOR_SIZE]; > +}; > + > +#define FS_IOC_SET_ENCRYPTION_POLICY _IOR('f', 19, struct fscrypt_policy) > +#define FS_IOC_GET_ENCRYPTION_PWSALT _IOW('f', 20, __u8[16]) > +#define FS_IOC_GET_ENCRYPTION_POLICY _IOW('f', 21, struct fscrypt_policy) > + > +/* Parameters for passing an encryption key into the kernel keyring */ > +#define FS_KEY_DESC_PREFIX "fscrypt:" > +#define FS_KEY_DESC_PREFIX_SIZE 8 > + > +/* Structure that userspace passes to the kernel keyring */ > +#define FS_MAX_KEY_SIZE 64 > + > +struct fscrypt_key { > + __u32 mode; > + __u8 raw[FS_MAX_KEY_SIZE]; > + __u32 size; > +}; > + > +#endif /* _UAPI_LINUX_FSCRYPT_H */ > -- > 2.15.0.rc0.271.g36b669edcc-goog >
next prev parent reply other threads:[~2017-10-27 18:01 UTC|newest] Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-23 21:40 [RFC PATCH 00/25] fscrypt: filesystem-level keyring and v2 policy support Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 01/25] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h> Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 18:01 ` Michael Halcrow [this message] 2017-10-27 18:01 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 02/25] fscrypt: use FSCRYPT_ prefix for uapi constants Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 18:02 ` Michael Halcrow 2017-10-27 18:02 ` Michael Halcrow via Linux-f2fs-devel 2017-10-27 18:02 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 03/25] fscrypt: use FSCRYPT_* definitions, not FS_* Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 18:06 ` Michael Halcrow 2017-10-27 18:06 ` Michael Halcrow 2017-10-27 18:06 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 04/25] fscrypt: refactor finding and deriving key Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 18:23 ` Michael Halcrow 2017-10-27 18:23 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 05/25] fs: add ->s_master_keys to struct super_block Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 18:26 ` Michael Halcrow 2017-10-27 18:26 ` Michael Halcrow 2017-10-27 18:26 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 06/25] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 20:14 ` Michael Halcrow 2017-10-27 20:14 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 07/25] fs/inode.c: export inode_lru_list_del() Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-27 20:28 ` Michael Halcrow 2017-10-27 20:28 ` Michael Halcrow 2017-10-27 20:28 ` Michael Halcrow 2017-10-23 21:40 ` [RFC PATCH 08/25] fs/inode.c: rename and export dispose_list() Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 09/25] fs/dcache.c: add shrink_dcache_inode() Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 10/25] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 11/25] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 12/25] ext4 crypto: wire up new ioctls for managing encryption keys Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 13/25] f2fs " Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 14/25] ubifs " Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 15/25] fscrypt: add UAPI definitions to get/set v2 encryption policies Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 16/25] fscrypt: implement basic handling of " Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 17/25] fscrypt: add an HKDF-SHA512 implementation Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 18/25] fscrypt: allow adding and removing keys for v2 encryption policies Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 19/25] fscrypt: use HKDF-SHA512 to derive the per-file keys for v2 policies Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 20/25] fscrypt: allow unprivileged users to add/remove " Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 21/25] fscrypt: require that key be added when setting a v2 encryption policy Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 22/25] ext4 crypto: wire up FS_IOC_GET_ENCRYPTION_POLICY_EX Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 23/25] f2fs " Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 24/25] ubifs " Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` [RFC PATCH 25/25] fscrypt: document the new ioctls and policy version Eric Biggers 2017-10-23 21:40 ` Eric Biggers 2017-10-23 21:40 ` 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=20171027180141.GA10611@google.com \ --to=mhalcrow@google.com \ --cc=ebiggers3@gmail.com \ --cc=ebiggers@google.com \ --cc=gwendal@chromium.org \ --cc=hashimoto@chromium.org \ --cc=jaegeuk@kernel.org \ --cc=keyrings@vger.kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-ext4@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ --cc=linux-fscrypt@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=ndesaulniers@google.com \ --cc=sarthakkukreti@chromium.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: linkBe 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.