From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git pile 7 (tmpfile)
Date: Sat, 8 Oct 2022 02:23:34 +0100 [thread overview]
Message-ID: <Y0DRFtPcQ2jeZfXa@ZenIV> (raw)
Miklos' ->tmpfile() signature change; pass an unopened struct file
to it, let it open the damn thing. Allows to add tmpfile support to FUSE.
A couple of conflicts - one in overlayfs (use the lines from this
branch), another in Documentation/filesystems/porting.rst (file is essentially
append-only, so just add the chunk to the EOF).
The following changes since commit 521a547ced6477c54b4b0cc206000406c221b4d6:
Linux 6.0-rc6 (2022-09-18 13:44:14 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-tmpfile
for you to fetch changes up to 7d37539037c2fca70346fbedc219f655253d5cff:
fuse: implement ->tmpfile() (2022-09-24 07:00:00 +0200)
----------------------------------------------------------------
tmpfile API change
----------------------------------------------------------------
Al Viro (1):
hugetlbfs: cleanup mknod and tmpfile
Miklos Szeredi (9):
vfs: add vfs_tmpfile_open() helper
cachefiles: tmpfile error handling cleanup
cachefiles: only pass inode to *mark_inode_inuse() helpers
cachefiles: use vfs_tmpfile_open() helper
ovl: use vfs_tmpfile_open() helper
vfs: make vfs_tmpfile() static
vfs: move open right after ->tmpfile()
vfs: open inside ->tmpfile()
fuse: implement ->tmpfile()
Documentation/filesystems/locking.rst | 3 +-
Documentation/filesystems/porting.rst | 10 +++
Documentation/filesystems/vfs.rst | 6 +-
fs/bad_inode.c | 2 +-
fs/btrfs/inode.c | 8 +--
fs/cachefiles/namei.c | 122 +++++++++++++++-------------------
fs/dcache.c | 4 +-
fs/ext2/namei.c | 6 +-
fs/ext4/namei.c | 6 +-
fs/f2fs/namei.c | 13 ++--
fs/fuse/dir.c | 24 ++++++-
fs/fuse/fuse_i.h | 3 +
fs/hugetlbfs/inode.c | 42 +++++-------
fs/minix/namei.c | 6 +-
fs/namei.c | 88 +++++++++++++++---------
fs/overlayfs/copy_up.c | 108 ++++++++++++++++--------------
fs/overlayfs/overlayfs.h | 14 ++--
fs/overlayfs/super.c | 10 +--
fs/overlayfs/util.c | 2 +-
fs/ramfs/inode.c | 6 +-
fs/ubifs/dir.c | 7 +-
fs/udf/namei.c | 6 +-
fs/xfs/xfs_iops.c | 16 +++--
include/linux/dcache.h | 3 +-
include/linux/fs.h | 16 ++++-
include/uapi/linux/fuse.h | 6 +-
mm/shmem.c | 6 +-
27 files changed, 303 insertions(+), 240 deletions(-)
next reply other threads:[~2022-10-08 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 1:23 Al Viro [this message]
2022-10-11 3:43 ` [git pull] vfs.git pile 7 (tmpfile) pr-tracker-bot
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=Y0DRFtPcQ2jeZfXa@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.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