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 4 (file_inode)
Date: Tue, 4 Oct 2022 17:56:10 +0100 [thread overview]
Message-ID: <YzxlqrEtoV37hm3l@ZenIV> (raw)
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_inode
for you to fetch changes up to 4094d98e3375833737b467998219338ffd46a68b:
orangefs: use ->f_mapping (2022-09-01 17:46:06 -0400)
----------------------------------------------------------------
whack-a-mole: cropped up open-coded file_inode() uses...
----------------------------------------------------------------
Al Viro (8):
ibmvmc: don't open-code file_inode()
exfat_iterate(): don't open-code file_inode(file)
sgx: use ->f_mapping...
bprm_fill_uid(): don't open-code file_inode()
nfs_finish_open(): don't open-code file_inode()
dma_buf: no need to bother with file_inode()->i_mapping
_nfs42_proc_copy(): use ->f_mapping instead of file_inode()->i_mapping
orangefs: use ->f_mapping
arch/x86/kernel/cpu/sgx/encl.c | 3 +--
drivers/dma-buf/udmabuf.c | 2 +-
drivers/misc/ibmvmc.c | 6 ++++--
fs/exec.c | 3 +--
fs/exfat/dir.c | 6 +++---
fs/nfs/dir.c | 2 +-
fs/nfs/nfs42proc.c | 2 +-
fs/orangefs/file.c | 4 +---
8 files changed, 13 insertions(+), 15 deletions(-)
next reply other threads:[~2022-10-04 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 16:56 Al Viro [this message]
2022-10-07 0:36 ` [git pull] vfs.git pile 4 (file_inode) 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=YzxlqrEtoV37hm3l@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;
as well as URLs for NNTP newsgroup(s).