From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git misc pile
Date: Thu, 11 Jan 2024 10:21:41 +0000 [thread overview]
Message-ID: <20240111102141.GY1674809@ZenIV> (raw)
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-misc
for you to fetch changes up to c5f3fd21789cff8fa1120e802dd1390d34e3eec0:
apparmorfs: don't duplicate kfree_link() (2023-12-21 12:53:43 -0500)
----------------------------------------------------------------
misc cleanups (the part that hadn't been picked by individual fs trees)
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (17):
zonefs: d_splice_alias() will do the right thing on ERR_PTR() inode
nilfs2: d_obtain_alias(ERR_PTR(...)) will do the right thing...
bfs_add_entry(): get rid of pointless ->d_name.len checks
nfsd: kill stale comment about simple_fill_super() requirements
udf: d_splice_alias() will do the right thing on ERR_PTR() inode
udf: d_obtain_alias(ERR_PTR(...)) will do the right thing...
udf_fiiter_add_entry(): check for zero ->d_name.len is bogus...
hostfs: use d_splice_alias() calling conventions to simplify failure exits
/proc/sys: use d_splice_alias() calling conventions to simplify failure exits
affs: d_obtain_alias(ERR_PTR(...)) will do the right thing
befs: d_obtain_alias(ERR_PTR(...)) will do the right thing
ext4_add_entry(): ->d_name.len is never 0
__ocfs2_add_entry(), ocfs2_prepare_dir_for_insert(): namelen checks
reiserfs_add_entry(): get rid of pointless namelen checks
ocfs2_find_match(): there's no such thing as NULL or negative ->d_parent
orangefs: saner arguments passing in readdir guts
apparmorfs: don't duplicate kfree_link()
fs/affs/namei.c | 3 ---
fs/befs/linuxvfs.c | 3 ---
fs/bfs/dir.c | 5 -----
fs/ext4/namei.c | 2 --
fs/hostfs/hostfs_kern.c | 8 ++------
fs/nfsd/nfsctl.c | 4 ----
fs/nilfs2/namei.c | 7 +------
fs/ocfs2/dcache.c | 7 -------
fs/ocfs2/dir.c | 9 ---------
fs/orangefs/dir.c | 32 ++++++++++++--------------------
fs/proc/proc_sysctl.c | 14 ++------------
fs/reiserfs/namei.c | 7 -------
fs/udf/namei.c | 11 +----------
fs/zonefs/super.c | 2 --
security/apparmor/apparmorfs.c | 7 +------
15 files changed, 19 insertions(+), 102 deletions(-)
next reply other threads:[~2024-01-11 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 10:21 Al Viro [this message]
2024-01-12 5:07 ` [git pull] vfs.git misc pile pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 4:29 Al Viro
2023-04-25 2:49 ` pr-tracker-bot
2022-12-12 0:39 Al Viro
2022-12-13 3:49 ` 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=20240111102141.GY1674809@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@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).