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 vfs fixes
Date: Wed, 11 Jan 2012 05:23:40 +0000 [thread overview]
Message-ID: <20120111052340.GG23916@ZenIV.linux.org.uk> (raw)
Assorted bug fixes (probably all of that should be -stable fodder, with
the exception of kmemleak cosmetical one). The usual place,
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
Shortlog:
Al Viro (7):
securityfs: fix object creation races
coda: deal correctly with allocation failure from coda_cnode_makectl()
coda: switch coda_cnode_make() to sane API as well, clean coda_lookup()
hfsplus: creation of hidden dir on mount can fail
autofs4: autofs4_wait() vs. autofs4_catatonic_mode() race
autofs4: catatonic_mode vs. notify_daemon race
autofs4: deal with autofs4_write/autofs4_write races
Miklos Szeredi (1):
fix shrink_dcache_parent() livelock
Sergey Senozhatsky (1):
block_dev: Suppress bdev_cache_init() kmemleak warninig
Diffstat:
fs/autofs4/autofs_i.h | 1 +
fs/autofs4/inode.c | 1 +
fs/autofs4/waitq.c | 40 ++++++----
fs/block_dev.c | 10 +--
fs/coda/cnode.c | 38 ++++------
fs/coda/coda_fs_i.h | 4 +-
fs/coda/dir.c | 29 +++----
fs/coda/inode.c | 10 ++-
fs/dcache.c | 15 +++-
fs/hfsplus/super.c | 11 ++-
include/linux/dcache.h | 1 +
security/inode.c | 191 +++++++++++++-----------------------------------
12 files changed, 137 insertions(+), 214 deletions(-)
next reply other threads:[~2012-01-11 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 5:23 Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 13:28 [git pull] more vfs fixes Al Viro
2011-03-09 4:57 Al Viro
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=20120111052340.GG23916@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).