From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 10/12] docs: ioctl-number: update FS entries
Date: Wed, 18 Nov 2026 21:04:35 -0800 [thread overview]
Message-ID: <20261119050444.249752-11-rdunlap@infradead.org> (raw)
In-Reply-To: <20261119050444.249752-1-rdunlap@infradead.org>
Update the list of files where filesystem ioctls are defined and update
the ranges of function numbers that are used.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
v2: address sashiko review comment (ext4 00-2F range referred to
the wrong file name)
[Since having multiple maintainers trying to merge these would
cause some conflicts, it would be more manageable for Jon to
take all of these through the docs-next tree.]
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Cc: Mike Marshall <hubcap@omnibond.com>
Cc: devel@lists.orangefs.org
Cc: Paulo Alcantara <pc@manguebit.org>
Cc: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-cifs@vger.kernel.org
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Documentation/userspace-api/ioctl/ioctl-number.rst | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
--- linux-next-20261116.orig/Documentation/userspace-api/ioctl/ioctl-number.rst
+++ linux-next-20261116/Documentation/userspace-api/ioctl/ioctl-number.rst
@@ -185,6 +185,7 @@ Code Seq# Include File
'I' all linux/isdn.h conflict!
'I' 00-0F drivers/isdn/divert/isdn_divert.h conflict!
'I' 40-4F linux/mISDNif.h conflict!
+'I' 00 linux/inotify.h
'K' all linux/kd.h
'L' 00-1F linux/loop.h conflict!
'L' 10-21 drivers/scsi/mpt3sas/mpt3sas_ctl.h conflict!
@@ -274,7 +275,7 @@ Code Seq# Include File
'f' 00-1F linux/ext2_fs.h conflict!
'f' 00-1F linux/ext3_fs.h conflict!
'f' 00-0F fs/jfs/jfs_dinode.h conflict!
-'f' 00-0F fs/ext4/ext4.h conflict!
+'f' 00-2F fs/ext4/ext4.h, uapi/linux/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
@@ -299,6 +300,7 @@ Code Seq# Include File
'k' 00-0F linux/spi/spidev.h conflict!
'k' 00-05 video/kyro.h conflict!
'k' 10-17 linux/hsi/hsi_char.h HSI character device
+'k' 01-0F fs/orangefs/protocol.h <mailto:devel@lists.orangefs.org>
'l' 00-3F linux/tcfs_fs.h transparent cryptographic file system
<http://web.archive.org/web/%2A/http://mikonos.dia.unisa.it/tcfs>
'l' 40-7F linux/udf_fs_i.h in development:
@@ -372,7 +374,7 @@ Code Seq# Include File
0x92 00-0F drivers/usb/mon/mon_bin.c
0x93 60-7F linux/auto_fs.h
0x94 all fs/btrfs/ioctl.h Btrfs filesystem
- and linux/fs.h some lifted to vfs/generic
+0x94 all linux/fs.h some lifted from Btrfs to vfs/generic
0x97 00-7F fs/ceph/ioctl.h Ceph file system
0x99 00-0F 537-Addinboard driver
<mailto:buk@buks.ipn.de>
@@ -440,7 +442,7 @@ Code Seq# Include File
0xCC 00-0F drivers/misc/ibmvmc.h pseries VMC driver
0xCD 01 linux/reiserfs_fs.h Dead since 6.13
0xCE 01-02 uapi/linux/cxl_mem.h Compute Express Link Memory Devices
-0xCF 02 fs/smb/client/cifs_ioctl.h
+0xCF 01-0F fs/smb/client/cifs_ioctl.h <mailto:linux-cifs@vger.kernel.org>
0xDD 00-3F ZFCP device driver see drivers/s390/scsi/
<mailto:aherrman@de.ibm.com>
0xE5 00-3F linux/fuse.h
@@ -449,6 +451,7 @@ Code Seq# Include File
0xEF 00-0F uapi/linux/ntfs.h NTFS
0xF3 00-3F drivers/usb/misc/sisusbvga/sisusb.h sisfb
0xF3 00-3F video/sisfb.h <mailto:thomas@winischhofer.net>
+0xF5 01-1F uapi/linux/f2fs.h <mailto:linux-f2fs-devel@lists.sourceforge.net>
0xF6 all LTTng Linux Trace Toolkit Next Generation
<mailto:mathieu.desnoyers@efficios.com>
0xF8 all arch/x86/include/uapi/asm/amd_hsmp.h AMD HSMP EPYC system management interface driver
next prev parent reply other threads:[~2026-11-19 5:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 5:04 [PATCH v2 00/12] docs: ioctl-number: update entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 01/12] docs: ioctl-number: update MM entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 02/12] docs: ioctl-number: update sound entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 03/12] docs: ioctl-number: update block entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 04/12] docs: ioctl-number: update networking entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 05/12] docs: ioctl-number: update video/fbdev entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 06/12] docs: ioctl-number: update SCSI entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 07/12] docs: ioctl-number: update MTD entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 08/12] docs: ioctl-number: update USB entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 09/12] docs: ioctl-number: update virtualization entries Randy Dunlap
2026-11-19 5:04 ` Randy Dunlap [this message]
2026-11-19 5:04 ` [PATCH v2 11/12] docs: ioctl-number: update platform entries Randy Dunlap
2026-11-19 5:04 ` [PATCH v2 12/12] docs: ioctl-number: update DRM entries Randy Dunlap
2026-11-19 5:35 [PATCH v2 00/12 RESEND] docs: ioctl-number: update entries Randy Dunlap
2026-11-19 5:35 ` [PATCH v2 10/12] docs: ioctl-number: update FS entries Randy Dunlap
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=20261119050444.249752-11-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®