linux-kernel - [git pull] vfs/fs for -rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 5 Jun 2010 03:58:27 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: [git pull] vfs/fs for -rc2

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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/