linux-kernel - [git pull] vfs fixes

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:	Fri, 29 Jan 2010 02:39:49 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [git pull] vfs fixes

Assorted filesystem fixes (mostly around ->get_sb() and ->remount_fs())
Please, pull from
git.kernel.org://pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus

Shortlog:
Al Viro (8):
      Fix a leak in affs_fill_super()
      Fix remount races with symlink handling in affs
      fix affs parse_options()
      Fix failure exits in bfs_fill_super()
      get rid of pointless checks after simple_pin_fs()
      fix leak in romfs_fill_super()
      fix oops in fs/9p late mount failure
      Fix failure exit in ipathfs

Diffstat:
 drivers/infiniband/hw/ipath/ipath_fs.c |    4 +--
 fs/9p/vfs_super.c                      |    3 +-
 fs/affs/affs.h                         |    2 +-
 fs/affs/namei.c                        |    7 +++-
 fs/affs/super.c                        |   31 ++++++++++++++++------
 fs/affs/symlink.c                      |    7 +++-
 fs/bfs/inode.c                         |   43 +++++++++++++++----------------
 fs/debugfs/inode.c                     |   11 +------
 fs/romfs/super.c                       |    1 +
 security/inode.c                       |   11 +------
 10 files changed, 62 insertions(+), 58 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/