public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-fsdevel@vger.kernel.org, brauner@kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>, linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/7] filesystem visibililty ioctls
Date: Tue,  6 Feb 2024 21:56:14 -0500	[thread overview]
Message-ID: <20240207025624.1019754-1-kent.overstreet@linux.dev> (raw)

ok, any further bikeshedding better be along the lines of "this will
cause a gaping security hole unless addressed" ;)

changes since v2:
 - now using nak (0x15) ioctl range; documentation updated
 - new helpers for setting the sysfs name
 - sysfs name uuid now has a length field

other notes:
 - fscrypt usage of s_uuid has justification, so we don't need to be
   concerned about exporting that (more) to userspace
 - i haven't updated btrfs for FS_IOC_SYSFS_NAME, less familiar with
   their code so they are cc'd
   ext4 may want this too?

Kent Overstreet (7):
  fs: super_set_uuid()
  overlayfs: Convert to super_set_uuid()
  fs: FS_IOC_GETUUID
  fat: Hook up sb->s_uuid
  fs: FS_IOC_GETSYSFSNAME
  xfs: add support for FS_IOC_GETSYSFSNAME
  bcachefs: add support for FS_IOC_GETSYSFSNAME

 .../userspace-api/ioctl/ioctl-number.rst      |  3 +-
 fs/bcachefs/fs.c                              |  3 +-
 fs/ext4/super.c                               |  2 +-
 fs/f2fs/super.c                               |  2 +-
 fs/fat/inode.c                                |  3 ++
 fs/gfs2/ops_fstype.c                          |  2 +-
 fs/ioctl.c                                    | 33 ++++++++++++
 fs/kernfs/mount.c                             |  4 +-
 fs/ocfs2/super.c                              |  4 +-
 fs/overlayfs/util.c                           | 14 +++--
 fs/ubifs/super.c                              |  2 +-
 fs/xfs/xfs_mount.c                            |  4 +-
 include/linux/fs.h                            | 51 +++++++++++++++++++
 include/uapi/linux/fs.h                       | 27 ++++++++++
 mm/shmem.c                                    |  4 +-
 15 files changed, 142 insertions(+), 16 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-02-07  2:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07  2:56 Kent Overstreet [this message]
2024-02-07  2:56 ` [PATCH v3 1/7] fs: super_set_uuid() Kent Overstreet
2024-02-08 10:11   ` Christian Brauner
2024-02-07  2:56 ` [PATCH v3 2/7] overlayfs: Convert to super_set_uuid() Kent Overstreet
2024-02-07  2:56 ` [PATCH v3 3/7] fs: FS_IOC_GETUUID Kent Overstreet
2024-02-07  6:41   ` Amir Goldstein
2024-02-07  6:46     ` Amir Goldstein
2024-02-08  9:44       ` Christian Brauner
2024-02-07  2:56 ` [PATCH v3 4/7] fat: Hook up sb->s_uuid Kent Overstreet
2024-02-07  2:56 ` [PATCH v3 5/7] fs: FS_IOC_GETSYSFSNAME Kent Overstreet
2024-02-08 10:09   ` Christian Brauner
2024-02-07  2:56 ` [PATCH v3 6/7] xfs: add support for FS_IOC_GETSYSFSNAME Kent Overstreet
2024-02-07  2:56 ` [PATCH v3 7/7] bcachefs: " Kent Overstreet
2024-02-08 10:20 ` [PATCH v3 0/7] filesystem visibililty ioctls Christian Brauner

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=20240207025624.1019754-1-kent.overstreet@linux.dev \
    --to=kent.overstreet@linux.dev \
    --cc=brauner@kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@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