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 misc dcache-related stuff
Date: Tue, 7 May 2019 21:33:55 +0100 [thread overview]
Message-ID: <20190507203355.GK23075@ZenIV.linux.org.uk> (raw)
Most of that pile is putting name length into struct name_snapshot
and making use of it. Beginning of that series ("ovl_lookup_real_one():
don't bother with strlen()") ought to have been split in two (separate
switch of name_snapshot to struct qstr from overlayfs reaping the trivial
benefits of that), but I wanted to avoid a rebase - by the time I'd spotted
that it was (a) in -next and (b) close to 5.1-final ;-/
The following changes since commit ce285c267a003acbf607f3540ff71287f82e5282:
autofs: fix use-after-free in lockless ->d_manage() (2019-04-09 19:18:19 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.dcache
for you to fetch changes up to 795d673af1afae8146ac3070a2d77cfae5287c43:
audit_compare_dname_path(): switch to const struct qstr * (2019-04-28 20:33:43 -0400)
----------------------------------------------------------------
Al Viro (10):
unexport d_alloc_pseudo()
nsfs: unobfuscate
sysv: bury the broken "quietly truncate the long filenames" logics
ovl_lookup_real_one(): don't bother with strlen()
switch fsnotify_move() to passing const struct qstr * for old_name
fsnotify(): switch to passing const struct qstr * for file_name
fsnotify: switch send_to_group() and ->handle_event to const struct qstr *
inotify_handle_event(): don't bother with strlen()
audit_update_watch(): switch to const struct qstr *
audit_compare_dname_path(): switch to const struct qstr *
Documentation/filesystems/porting | 5 +++++
fs/dcache.c | 18 +++++++++---------
fs/debugfs/inode.c | 2 +-
fs/internal.h | 1 +
fs/kernfs/file.c | 6 ++++--
fs/namei.c | 4 ++--
fs/notify/dnotify/dnotify.c | 2 +-
fs/notify/fanotify/fanotify.c | 2 +-
fs/notify/fsnotify.c | 8 ++++----
fs/notify/inotify/inotify.h | 2 +-
fs/notify/inotify/inotify_fsnotify.c | 6 +++---
fs/nsfs.c | 23 ++++++++++-------------
fs/overlayfs/export.c | 2 +-
fs/sysv/namei.c | 15 ---------------
fs/sysv/super.c | 3 ---
fs/sysv/sysv.h | 3 ---
include/linux/dcache.h | 3 +--
include/linux/fsnotify.h | 10 +++++-----
include/linux/fsnotify_backend.h | 6 +++---
kernel/audit.h | 2 +-
kernel/audit_fsnotify.c | 2 +-
kernel/audit_tree.c | 2 +-
kernel/audit_watch.c | 4 ++--
kernel/auditfilter.c | 6 +++---
kernel/auditsc.c | 4 ++--
25 files changed, 62 insertions(+), 79 deletions(-)
next reply other threads:[~2019-05-07 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 20:33 Al Viro [this message]
2019-05-08 4:55 ` [git pull] vfs.git misc dcache-related stuff 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=20190507203355.GK23075@ZenIV.linux.org.uk \
--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).