From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git pile 3 (file)
Date: Tue, 4 Oct 2022 17:54:56 +0100 [thread overview]
Message-ID: <YzxlYFiWmx5nK+gT@ZenIV> (raw)
The non-trivial part here is filldir_t calling conventions change.
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-file
for you to fetch changes up to 47091e4ed9af648d6cfa3a5f0809ece371294ecb:
dma_buf_getfile(): don't bother with ->f_flags reassignments (2022-08-17 17:25:54 -0400)
----------------------------------------------------------------
struct file-related stuff
----------------------------------------------------------------
Al Viro (2):
Change calling conventions for filldir_t
dma_buf_getfile(): don't bother with ->f_flags reassignments
Amir Goldstein (1):
locks: fix TOCTOU race when granting write lease
Documentation/filesystems/porting.rst | 11 ++++++
arch/alpha/kernel/osf_sys.c | 10 +++---
drivers/dma-buf/dma-buf.c | 2 +-
fs/afs/dir.c | 23 ++++++------
fs/ecryptfs/file.c | 38 +++++++++-----------
fs/exportfs/expfs.c | 7 ++--
fs/fat/dir.c | 8 ++---
fs/file_table.c | 7 +---
fs/gfs2/export.c | 6 ++--
fs/internal.h | 10 ++++++
fs/ksmbd/smb2pdu.c | 16 ++++-----
fs/ksmbd/vfs.c | 14 ++++----
fs/nfsd/nfs4recover.c | 8 ++---
fs/nfsd/vfs.c | 6 ++--
fs/ocfs2/dir.c | 10 +++---
fs/ocfs2/journal.c | 14 ++++----
fs/open.c | 11 +++---
fs/overlayfs/readdir.c | 28 +++++++--------
fs/readdir.c | 68 +++++++++++++++++------------------
fs/reiserfs/xattr.c | 20 +++++------
fs/xfs/scrub/dir.c | 8 ++---
fs/xfs/scrub/parent.c | 4 +--
include/linux/fs.h | 9 ++---
23 files changed, 169 insertions(+), 169 deletions(-)
next reply other threads:[~2022-10-04 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 16:54 Al Viro [this message]
2022-10-07 0:36 ` 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=YzxlYFiWmx5nK+gT@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®