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 15 - more non-uaccess bits
Date: Sat, 8 Jul 2017 01:30:36 +0100 [thread overview]
Message-ID: <20170708003036.GN10672@ZenIV.linux.org.uk> (raw)
Assorted normal VFS / filesystems stuff...
[this is not all; there are several branches left, but that's for tomorrow]
The following changes since commit 41f1830f5a7af77cf5c86359aba3cbd706687e52:
Linux 4.12-rc6 (2017-06-19 22:19:37 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to fetch changes up to 49d31c2f389acfe83417083e1208422b4091cd9e:
dentry name snapshots (2017-07-07 20:09:10 -0400)
----------------------------------------------------------------
Al Viro (1):
dentry name snapshots
Carlos Maiolino (1):
Make statfs properly return read-only state after emergency remount
Denys Vlasenko (1):
minix: Deinline get_block, save 2691 bytes
Kees Cook (1):
fs: Reorder inode_owner_or_capable() to avoid needless
Luis R. Rodriguez (1):
fs: warn in case userspace lied about modprobe return
Sebastian Andrzej Siewior (1):
fs/dcache: init in_lookup_hashtable
fs/dcache.c | 32 ++++++++++++++++++++++++++++++++
fs/debugfs/inode.c | 10 +++++-----
fs/filesystems.c | 4 +++-
fs/inode.c | 2 +-
fs/minix/itree_common.c | 2 +-
fs/namei.c | 10 +++++-----
fs/notify/fsnotify.c | 8 ++++++--
fs/statfs.c | 2 ++
include/linux/dcache.h | 6 ++++++
include/linux/fsnotify.h | 31 -------------------------------
10 files changed, 61 insertions(+), 46 deletions(-)
next reply other threads:[~2017-07-08 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:30 Al Viro [this message]
2017-07-08 6:14 ` [git pull] vfs.git pile 15 - more non-uaccess bits Amir Goldstein
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=20170708003036.GN10672@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 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.