linux-kernel - [patch 00/22] vfs: fixes and cleanups (v3)

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>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 16 May 2008 18:31:36 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	akpm@...ux-foundation.org
Cc:	hch@...radead.org, viro@...IV.linux.org.uk, ezk@...sunysb.edu,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [patch 00/22] vfs: fixes and cleanups (v3)

Changes since the last submission

  - drop patches already merged into mainline
  - Al pointed out problems with "vfs: truncate: append-only checking
    cleanup", drop it
  - re-add the security call into "fat: dont call notify_change" to be
    absolutely safe, but add comment noting this may not strictly be needed
  - small changes to "vfs: utimes cleanup", hopefully everyone will
    be happy with this

Thanks to Christoph and Al for the reviews.

The series contains the following changes:

1-7   filesystem cleanups/fixes, mainly removing vfs_* calls
8-12  vfs cleanups/fixes
13-22 add path_* helpers to check r/o bind mounts

It's against mainline and the 13-22 patches have a small conflict with
git-unionfs.patch.  They also break unionfs compilation.  Erez has a
patch for that, what are the preferred logistics for getting that into
-mm?

This series is also available from the following git tree:

  git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git vfs-cleanups

Thanks,
Miklos

--
--
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/