From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: "Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] docs: ioctl-number: document fscrypt ioctl numbers
Date: Mon, 21 Oct 2019 13:29:00 -0700 [thread overview]
Message-ID: <20191021202859.GD122863@gmail.com> (raw)
In-Reply-To: <20191009234555.226282-1-ebiggers@kernel.org>
On Wed, Oct 09, 2019 at 04:45:55PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> The 'f' ioctls with numbers 19-26 decimal are currently used for fscrypt
> (a.k.a. ext4/f2fs/ubifs encryption), and up to 39 decimal is reserved
> for future fscrypt use, as per the comment in fs/ext4/ext4.h. So the
> reserved range is 13-27 hex.
>
> Document this in ioctl-number.rst.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> Documentation/ioctl/ioctl-number.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/ioctl/ioctl-number.rst b/Documentation/ioctl/ioctl-number.rst
> index bef79cd4c6b4d..4ef86433bd677 100644
> --- a/Documentation/ioctl/ioctl-number.rst
> +++ b/Documentation/ioctl/ioctl-number.rst
> @@ -233,6 +233,7 @@ Code Seq# Include File Comments
> 'f' 00-0F fs/ext4/ext4.h conflict!
> 'f' 00-0F linux/fs.h conflict!
> 'f' 00-0F fs/ocfs2/ocfs2_fs.h conflict!
> +'f' 13-27 linux/fscrypt.h
> 'f' 81-8F linux/fsverity.h
> 'g' 00-0F linux/usb/gadgetfs.h
> 'g' 20-2F linux/usb/g_printer.h
> --
Applied to fscrypt.git for 5.5.
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org, "Theodore Y . Ts'o" <tytso@mit.edu>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] docs: ioctl-number: document fscrypt ioctl numbers
Date: Mon, 21 Oct 2019 13:29:00 -0700 [thread overview]
Message-ID: <20191021202859.GD122863@gmail.com> (raw)
In-Reply-To: <20191009234555.226282-1-ebiggers@kernel.org>
On Wed, Oct 09, 2019 at 04:45:55PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> The 'f' ioctls with numbers 19-26 decimal are currently used for fscrypt
> (a.k.a. ext4/f2fs/ubifs encryption), and up to 39 decimal is reserved
> for future fscrypt use, as per the comment in fs/ext4/ext4.h. So the
> reserved range is 13-27 hex.
>
> Document this in ioctl-number.rst.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> Documentation/ioctl/ioctl-number.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/ioctl/ioctl-number.rst b/Documentation/ioctl/ioctl-number.rst
> index bef79cd4c6b4d..4ef86433bd677 100644
> --- a/Documentation/ioctl/ioctl-number.rst
> +++ b/Documentation/ioctl/ioctl-number.rst
> @@ -233,6 +233,7 @@ Code Seq# Include File Comments
> 'f' 00-0F fs/ext4/ext4.h conflict!
> 'f' 00-0F linux/fs.h conflict!
> 'f' 00-0F fs/ocfs2/ocfs2_fs.h conflict!
> +'f' 13-27 linux/fscrypt.h
> 'f' 81-8F linux/fsverity.h
> 'g' 00-0F linux/usb/gadgetfs.h
> 'g' 20-2F linux/usb/g_printer.h
> --
Applied to fscrypt.git for 5.5.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-10-21 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 23:45 [PATCH] docs: ioctl-number: document fscrypt ioctl numbers Eric Biggers
2019-10-09 23:45 ` [f2fs-dev] " Eric Biggers
2019-10-21 20:29 ` Eric Biggers [this message]
2019-10-21 20:29 ` 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=20191021202859.GD122863@gmail.com \
--to=ebiggers@kernel.org \
--cc=jaegeuk@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=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.