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] more fixes for 3.0
Date: Mon, 18 Jul 2011 04:27:47 +0100 [thread overview]
Message-ID: <20110718032747.GX11013@ZenIV.linux.org.uk> (raw)
Assorted crap caught by ->d_parent audit (and there's more, unfortunately ;-/)
The stuff Hugh found is not in that pile, BTW. Please, pull from usual place:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus
Shortlog:
Al Viro (7):
cifs: build_path_from_dentry() race fix
ceph analog of cifs build_path_from_dentry() race fix
fix exofs ->get_parent()
ufs should use d_splice_alias()
cramfs: get_cramfs_inode() returns ERR_PTR() on failure
hppfs: fix dentry leak
hppfs_lookup(): don't open-code lookup_one_len()
Diffstat:
fs/ceph/mds_client.c | 19 ++++++++++++++++---
fs/cifs/dir.c | 13 ++++++++++++-
fs/cramfs/inode.c | 22 ++++++++++++----------
fs/exofs/super.c | 2 +-
fs/hppfs/hppfs.c | 31 +++++++++----------------------
fs/ufs/namei.c | 12 ++++--------
6 files changed, 54 insertions(+), 45 deletions(-)
reply other threads:[~2011-07-18 3:27 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=20110718032747.GX11013@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).