All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Cc: Nathan Scott <nathans@debian.org>
Subject: xfsprogs-3.1.11 pre-release   please test!
Date: Tue, 30 Apr 2013 15:01:23 -0500	[thread overview]
Message-ID: <51802313.40507@sgi.com> (raw)

Hi Folks,

Here are the changes for this release:

xfsprogs-3.1.11 (30 April 2013)

         - Support for relative paths in xfs_quota thanks to Satoru 
Takeuchi.
         - mkfs.xfs will always go into multidisk mode when filesystem
           geometry is specified on the command line.
         - Document all commands in xfs_io.
         - Remove setfl command from xfs_io.
         - xfs_metadump will obfuscate symlinks by path component.
         - mkfs.xfs no longer accepts geometry settings smaller than the
           physical sector size.
         - xfs_logprint now supports multiply-logged inode fields and
           handles continued inode transactions correctly.
         - kill XLOG_SET
         - Update release scripts to use git archive to address a
           missing source file reported by Arkadiusz Mi?kiewicz
         - Fix a build error with -Werror=format-security, reported
           by Arkadiusz Mi?kiewicz
         - mkfs.xfs no longer attempts to discard when -N option is used.
         - Update 'make deb' to use tarball
         - Sync up with log reservation changes in the kernel.
         - Fix possible unallocated memory access in fiemap.
         - Guard against string overflow in path_to_fspath.
         - Fix setup_cursor array allocation.
         - Fix free of unintialized pointer in xfs_acl_valid error path.
         - Guard against path string overflows.
         - Check strdup results properly in initallfs().
         - Fix attribute no_change_count logic.
         - Remove extraneous close() in fsrallfs().
         - xfs_repair now skips the freelist scan of a corrupt agf
           when in no-modify mode.
         - xfs_db now skips freelist scans of corrupt agfs.
         - Remove unconditional ASSERT(0) in xfs_repair.
         - Reduce bb_numrecs in bno/cnt btrees when log consumes all agf 
space.
         - Add depraction message for xfs_check.
         - xfs_quota allow user or group names beginning with digits 
reported by
           James Carter.
         - Fix manpages and usage() spelling, errors and omissions.

I have placed a pre-release tarball here:

ftp://oss.sgi.com/projects/xfs/cmd_tars/pre-release/xfsprogs-pre-3.1.11-3.tar.gz

Please take a look and report any issues before next Wednesday (08 May 
2013).  If there are other patches which you feel are essential, now is 
the time to say so.

Regards
--Rich

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-04-30 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 20:01 Rich Johnston [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-01 20:12 xfsprogs-3.1.11 pre-release please test! Rich Johnston
2013-05-01 20:35 ` Mark Tinguely
2013-05-01 21:01   ` Eric Sandeen
2013-05-01 21:17     ` Mark Tinguely
2013-05-01 21:23       ` Eric Sandeen
2013-05-01 22:10         ` Dave Chinner
2013-05-02 13:34   ` Michael L. Semon
2013-05-02 14:45     ` Eric Sandeen

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=51802313.40507@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=nathans@debian.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.