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/fs for -rc2
Date: Sat, 5 Jun 2010 03:58:27 +0100 [thread overview]
Message-ID: <20100605025827.GI31073@ZenIV.linux.org.uk> (raw)
Fixes and two really obvious cleanups; please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus
Shortlog:
Al Viro (2):
mqueue doesn't need make_bad_inode()
fix the deadlock in qib_fs
Andrew Hendry (1):
Minix: Clean up left over label
Dan Carpenter (1):
fcntl: return -EFAULT if copy_to_user fails
Nick Piggin (2):
fix setattr error handling in sysfs, configfs
fix truncate inode time modification breakage
Roberto Sassu (1):
wrong type for 'magic' argument in simple_fill_super()
Diffsstat:
drivers/infiniband/hw/qib/qib_fs.c | 4 +---
fs/configfs/inode.c | 9 ++++-----
fs/ext2/inode.c | 2 +-
fs/fcntl.c | 7 +++++--
fs/libfs.c | 3 ++-
fs/minix/dir.c | 4 ----
fs/sysfs/inode.c | 6 ++++--
include/linux/fs.h | 2 +-
ipc/mqueue.c | 1 -
mm/shmem.c | 5 +++--
10 files changed, 21 insertions(+), 22 deletions(-)
reply other threads:[~2010-06-05 2:58 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=20100605025827.GI31073@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