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:	Mon, 27 Jun 2011 09:00:56 -0500
From:	Alex Elder <aelder@....com>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, xfs@....sgi.com,
	akpm@...ux-foundation.org
Subject: [GIT PULL] XFS update for 3.0-rc5

Linus, please pull the following three XFS changes for 3.0-rc5:
- The first fixes a problem where certain XFS inode fields were
  not getting re-initialized when they were recycled.
- The second ensures a flag related to speculatively preallocating
  space beyond EOF gets reset when a file is truncated.
- The third properly sets a flag indicating that a lookup failure
  is allowed for user-supplied attribute names.  This was causing
  a failed assertion when running a test that attempts to remove
  a non-existent selinux-related attribute.

Thank you.

  					-Alex

The following changes since commit 258e43fdb00c73d424b114ae3850accd55b27cbb:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/sfrench/cifs-2.6 (2011-06-26 19:40:31 -0700)

are available in the git repository at:

  git://oss.sgi.com/xfs/xfs for-linus

Dave Chinner (3):
      xfs: reset inode per-lifetime state when recycling it
      xfs: clear XFS_IDIRTY_RELEASE on truncate down
      xfs: prevent bogus assert when trying to remove non-existent attribute

 fs/xfs/xfs_attr.c     |    7 +++++++
 fs/xfs/xfs_iget.c     |   13 +++++++++----
 fs/xfs/xfs_inode.h    |   10 ++++++++++
 fs/xfs/xfs_vnodeops.c |    7 +++++--
 4 files changed, 31 insertions(+), 6 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ