From: Miklos Szeredi <mszeredi@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Amir Goldstein <amir73il@gmail.com>,
David Howells <dhowells@redhat.com>,
Yu-li Lin <yulilin@google.com>,
Chirantan Ekbote <chirantan@chromium.org>
Subject: [PATCH v3 0/9] fuse tmpfile
Date: Tue, 20 Sep 2022 21:36:23 +0200 [thread overview]
Message-ID: <20220920193632.2215598-1-mszeredi@redhat.com> (raw)
Al,
This should address your comments.
No xfstests regressions on xfs or overlayfs. Also tested overlayfs on
fuse.
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#fuse-tmpfile-v3
V3:
- add bits to Documentation/
- add hugetlbfs cleanup
- overlayfs copy-up: move opening target file to caller
V2:
- rename finish_tmpfile() to finish_open_simple()
- fix warning reported by kernel test robot
- patch description improvements
---
Al Viro (1):
hugetlbfs: cleanup mknod and tmpfile
Miklos Szeredi (8):
cachefiles: tmpfile error handling cleanup
vfs: add tmpfile_open() helper
cachefiles: use tmpfile_open() helper
ovl: use 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 | 67 +++++++---------
fs/dcache.c | 4 +-
fs/ext2/namei.c | 6 +-
fs/ext4/namei.c | 6 +-
fs/f2fs/namei.c | 13 ++--
fs/fuse/dir.c | 25 +++++-
fs/fuse/fuse_i.h | 3 +
fs/hugetlbfs/inode.c | 42 ++++------
fs/minix/namei.c | 6 +-
fs/namei.c | 84 ++++++++++++--------
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, 279 insertions(+), 206 deletions(-)
--
2.37.3
next reply other threads:[~2022-09-20 19:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 19:36 Miklos Szeredi [this message]
2022-09-20 19:36 ` [PATCH v3 1/9] cachefiles: tmpfile error handling cleanup Miklos Szeredi
2022-09-20 19:36 ` [PATCH v3 2/9] hugetlbfs: cleanup mknod and tmpfile Miklos Szeredi
2022-09-21 7:59 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 3/9] vfs: add tmpfile_open() helper Miklos Szeredi
2022-09-21 8:09 ` Christian Brauner
2022-09-21 14:33 ` Miklos Szeredi
2022-09-20 19:36 ` [PATCH v3 4/9] cachefiles: use " Miklos Szeredi
2022-09-21 8:26 ` Christian Brauner
2022-09-21 14:44 ` Miklos Szeredi
2022-09-21 19:46 ` Al Viro
2022-09-22 8:04 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 5/9] ovl: " Miklos Szeredi
2022-09-21 8:35 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 6/9] vfs: make vfs_tmpfile() static Miklos Szeredi
2022-09-21 8:36 ` Christian Brauner
2022-09-20 19:36 ` [PATCH v3 7/9] vfs: move open right after ->tmpfile() Miklos Szeredi
2022-09-20 20:57 ` Al Viro
2022-09-21 3:06 ` Miklos Szeredi
2022-09-21 8:54 ` Christian Brauner
2022-09-21 14:53 ` Miklos Szeredi
2022-09-21 19:55 ` Al Viro
2022-09-21 9:03 ` Christian Brauner
2022-09-21 14:56 ` Miklos Szeredi
2022-09-21 15:09 ` Christian Brauner
2022-09-21 15:24 ` Miklos Szeredi
2022-09-20 19:36 ` [PATCH v3 8/9] vfs: open inside ->tmpfile() Miklos Szeredi
2022-09-21 9:08 ` Christian Brauner
2022-09-21 14:58 ` Miklos Szeredi
2022-09-21 15:07 ` Christian Brauner
2022-09-21 15:27 ` Miklos Szeredi
2022-09-21 15:36 ` Christian Brauner
2022-09-21 19:52 ` Al Viro
2022-09-20 19:36 ` [PATCH v3 9/9] fuse: implement ->tmpfile() Miklos Szeredi
2022-09-21 9:15 ` Christian Brauner
2022-09-21 15:00 ` Miklos Szeredi
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=20220920193632.2215598-1-mszeredi@redhat.com \
--to=mszeredi@redhat.com \
--cc=amir73il@gmail.com \
--cc=chirantan@chromium.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=yulilin@google.com \
/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;
as well as URLs for NNTP newsgroup(s).