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 and filesystem fixes
Date: Sat, 24 Aug 2013 19:30:52 +0100 [thread overview]
Message-ID: <20130824183052.GV27005@ZenIV.linux.org.uk> (raw)
Hopefully linux.org.uk mail setup got fixed and this one won't bounce...
Assorted fixes from the last week or so; please pull from the usual place -
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (1):
cope with potentially long ->d_dname() output for shmem/hugetlb
Dan Carpenter (3):
efs: iget_locked() doesn't return an ERR_PTR()
bfs: iget_locked() doesn't return an ERR_PTR
VFS: collect_mounts() should return an ERR_PTR
Oleg Nesterov (1):
proc: kill the extra proc_readfd_common()->dir_emit_dots()
Diffstat:
fs/bfs/inode.c | 2 +-
fs/dcache.c | 11 +++++++++++
fs/efs/inode.c | 2 +-
fs/hugetlbfs/inode.c | 8 +-------
fs/namespace.c | 2 +-
fs/proc/fd.c | 2 --
include/linux/dcache.h | 1 +
mm/shmem.c | 8 +-------
8 files changed, 17 insertions(+), 19 deletions(-)
reply other threads:[~2013-08-24 18:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130824183052.GV27005@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).