From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfsprogs: v3.2.4 released
Date: Thu, 30 Jul 2015 11:36:26 +1000 [thread overview]
Message-ID: <20150730013626.GL16638@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3097 bytes --]
Hi All.
xfsprogs v3.2.4 has just been released. This release contains only
changes to xfs_metadump to address the information leaks disclosed
in CVE-2012-2150 here:
https://marc.info/?l=oss-security&m=143766249112576&w=2
Many thanks go to Eric Sandeen for doing all the work to address
these issues, and to Brian Foster, Christoph Hellwig and Darrick
Wong for reviewing the changes.
The source code can be accessed via git using either of these URLs:
git://oss.sgi.com/xfs/cmds/xfsprogs.git
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
and the release is tagged with the "v3.2.4" tag to make it easy to
check out the exact source used for the release.
A signed gzipped-tar archive of the source code is available
here:
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-3.2.4.tar.gz
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-3.2.4.tar.gz.sign
The archive is signed with my gpg key (the same one that this
release announcement is signed with).
Problems, issues, questions and general discussion about the release
should be directed to the XFS mailing list (xfs@oss.sgi.com).
-Dave.
The new head of the master branch is commit:
4a2f31a xfsprogs: Release v3.2.4
New Commits:
Dave Chinner (1):
[4a2f31a] xfsprogs: Release v3.2.4
Eric Sandeen (19):
[7ac353a] libxlog: add xlog_is_empty() helper
[ffc56f1] metadump: rename dont_obfuscate variable
[190df61] metadump: zero out clean log
[37a7818] xfs_metadump: don't zero log if not obfuscating
[80917c1] xfs_metadump: obfuscate remote symlinks on CRC filesystems
[8085336] metadump: obfuscate attrs on CRC fs
[1941482] metadump: Fill attribute values with 'v' rather than NUL
[8927d44] metadump: Obfuscate the filesystem label
[aad766a] metadump: handle multi-block directories
[b09e839] metadump: Add option to copy metadata blocks intact
[75333d2] metadump: Copy the log if not obfuscating or zeroing
[18cdb61] metadump: Zero out unused portion of the AGFL
[27499a0] metadump: Zero literal area of unused inodes
[87c955c] metadump: Zero unused portions of inode literal area
[6d34e8b] metadump: Zero sparse/unused regions of dir2
[23b2ae2] metadump: Zero unused tail of symlink blocks
[70099c8] metadump: Zero unused portions of attribute blocks
[c83c169] metadump: Zero unused portions of DA_NODE blocks
[20f35ef] metadump: Zero unused portions of inode, BMAP, and allocation btree blocks
Code Diffstat:
VERSION | 2 +-
db/metadump.c | 475 +++++++++++++++++++++++++++++++++++++++++-------
db/sb.c | 25 +--
db/type.c | 3 +
db/type.h | 2 +-
db/xfs_metadump.sh | 5 +-
debian/changelog | 7 +
doc/CHANGES | 3 +
include/libxlog.h | 2 +
libxlog/util.c | 56 ++++++
man/man8/xfs_metadump.8 | 10 +-
11 files changed, 499 insertions(+), 91 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2015-07-30 1:36 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=20150730013626.GL16638@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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