public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-fsdevel@vger.kernel.org
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Jens Axboe <axboe@kernel.dk>
Subject: [PATCHES][RFC] statx-related stuff
Date: Tue, 12 Nov 2024 20:21:18 +0000	[thread overview]
Message-ID: <20241112202118.GA3387508@ZenIV> (raw)

Assorted statx-related stuff; I hoped there would be more of that, but
the things got stalled.

Currently in there:
	* partial untangling of io_uring interactions (separating
the damn LOOKUP_EMPTY from the rest of flags, at least)
	* struct fd converions in the area (separated from #work.fd
to reduce conflicts)
	* getting rid of AT_GETATTR_NOSEC [Stefan Berger]; depending
upon the desired semantics for LSM shite around ->getattr() we might
want to pass some kind of flag to instances, but in the current form
it's been completely pointless - all calls ended up with that thing
passed to them.
	* getting rid of pointless empty_dir_getattr() - it's used
only as ->getattr() instance and it had been an equivalent of what
we do with NULL ->getattr all along.

Branch is on top of viro/vfs.git#base.getname-fixed; it lives in
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git #work.statx2
individual patches in followups.

Shortlog:
Al Viro (4):
      io_statx_prep(): use getname_uflags()
      kill getname_statx_lookup_flags()
      fs/stat.c: switch to CLASS(fd_raw)
      libfs: kill empty_dir_getattr()

Stefan Berger (1):
      fs: Simplify getattr interface function checking AT_GETATTR_NOSEC flag

Diffstat:
 fs/ecryptfs/inode.c        | 12 ++----------
 fs/internal.h              |  1 -
 fs/libfs.c                 | 11 -----------
 fs/overlayfs/inode.c       | 10 +++++-----
 fs/overlayfs/overlayfs.h   |  8 --------
 fs/stat.c                  | 24 +++++++-----------------
 include/uapi/linux/fcntl.h |  4 ----
 io_uring/statx.c           |  3 +--
 8 files changed, 15 insertions(+), 58 deletions(-)

             reply	other threads:[~2024-11-12 20:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 20:21 Al Viro [this message]
2024-11-12 20:25 ` [PATCH 1/5] io_statx_prep(): use getname_uflags() Al Viro
2024-11-12 20:25   ` [PATCH 2/5] kill getname_statx_lookup_flags() Al Viro
2024-11-13 10:20     ` Christian Brauner
2024-11-12 20:25   ` [PATCH 3/5] fs/stat.c: switch to CLASS(fd_raw) Al Viro
2024-11-13 10:20     ` Christian Brauner
2024-11-12 20:25   ` [PATCH 4/5] fs: Simplify getattr interface function checking AT_GETATTR_NOSEC flag Al Viro
2024-11-13 10:22     ` Christian Brauner
2024-11-12 20:25   ` [PATCH 5/5] libfs: kill empty_dir_getattr() Al Viro
2024-11-13 10:22     ` Christian Brauner
2024-11-13 10:20   ` [PATCH 1/5] io_statx_prep(): use getname_uflags() Christian Brauner
2024-11-13 14:07   ` Jens Axboe

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=20241112202118.GA3387508@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --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