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 6 (constification, mostly struct path)
Date: Tue, 4 Oct 2022 18:02:06 +0100 [thread overview]
Message-ID: <YzxnDoPjLjkuUlXp@ZenIV> (raw)
... with another constification patch stuck in the same branch
(->getprocattr() one)
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-path
for you to fetch changes up to 88569546e8a13a0c1ccf119dac72376784b0ea42:
ecryptfs: constify path (2022-09-01 17:40:38 -0400)
----------------------------------------------------------------
whack-a-mole: constifying struct path *
----------------------------------------------------------------
Al Viro (11):
->getprocattr(): attribute name is const char *, TYVM...
do_sys_name_to_handle(): constify path
may_linkat(): constify path
fs/notify: constify path
overlayfs: constify path
do_proc_readlink(): constify path
__io_setxattr(): constify path
audit_init_parent(): constify path
nd_jump_link(): constify path
spufs: constify path
ecryptfs: constify path
arch/powerpc/platforms/cell/spufs/inode.c | 6 +++---
arch/powerpc/platforms/cell/spufs/spufs.h | 2 +-
fs/ecryptfs/ecryptfs_kernel.h | 2 +-
fs/ecryptfs/file.c | 2 +-
fs/ecryptfs/inode.c | 2 +-
fs/ecryptfs/main.c | 2 +-
fs/fhandle.c | 2 +-
fs/internal.h | 2 +-
fs/namei.c | 4 ++--
fs/notify/fanotify/fanotify.c | 2 +-
fs/notify/fanotify/fanotify.h | 2 +-
fs/notify/fanotify/fanotify_user.c | 6 +++---
fs/overlayfs/copy_up.c | 12 ++++++------
fs/overlayfs/file.c | 2 +-
fs/overlayfs/inode.c | 6 +++---
fs/overlayfs/namei.c | 4 ++--
fs/overlayfs/overlayfs.h | 22 +++++++++++-----------
fs/overlayfs/readdir.c | 16 ++++++++--------
fs/overlayfs/super.c | 8 ++++----
fs/overlayfs/util.c | 10 +++++-----
fs/proc/base.c | 4 ++--
include/linux/lsm_hook_defs.h | 2 +-
include/linux/namei.h | 2 +-
include/linux/security.h | 4 ++--
io_uring/xattr.c | 2 +-
kernel/audit_watch.c | 2 +-
security/apparmor/lsm.c | 2 +-
security/security.c | 4 ++--
security/selinux/hooks.c | 2 +-
security/smack/smack_lsm.c | 2 +-
30 files changed, 70 insertions(+), 70 deletions(-)
next reply other threads:[~2022-10-04 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 17:02 Al Viro [this message]
2022-10-07 0:36 ` [git pull] vfs.git pile 6 (constification, mostly struct path) 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=YzxnDoPjLjkuUlXp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.