public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: [GIT PULL] xfs: fixes for 3.14-rc3
Date: Sat, 22 Feb 2014 09:59:43 +1100	[thread overview]
Message-ID: <20140221225943.GR13647@dastard> (raw)

Hi Linus,

This is the first pull request I've had to do for you, so I'm still
sorting things out. The reason I'm sending this and not Ben should
be obvious from the first commit below - SGI has stepped down from
the XFS maintainership role. As such, I'd like to take another
opportunity to thank them for their many years of effort maintaining
XFS and supporting the XFS community that they developed from the
ground up.

So I haven't had time to work things like signed tags into my
workflows yet, so this is just a repo branch I'm asking you to pull
from. And yes, I named the branch -rc4 because I wanted the fixes in
-rc4, not because the branch was for merging into -rc3. Probably not
right, either.

Anyway, I should have everything sorted out by the time the next
merge window comes around. If there's anything that you don't like
in the pull req, feel free to flame me unmercifully.

The changes are fixes for recent regressions and important thinkos
in verification code:

	- a log vector buffer alignment issue on ia32
	- timestamps on truncate got mangled
	- primary superblock CRC validation fixes and error message
	  sanitisation

Cheers,

Dave.

The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:

  Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)

are available in the git repository at:

  git://oss.sgi.com/xfs/xfs.git xfs-fixes-for-3.14-rc4

for you to fetch changes up to 5ef11eb0700f806c4671ba33e5befa784a2f70ef:

  xfs: limit superblock corruption errors to actual corruption (2014-02-19 15:39:35 +1100)

----------------------------------------------------------------
Ben Myers (1):
      MAINTAINERS: SGI no longer maintaining XFS

Christoph Hellwig (1):
      xfs: ensure correct timestamp updates from truncate

Dave Chinner (1):
      xfs: ensure correct log item buffer alignment

Eric Sandeen (3):
      xfs: xfs_sb_read_verify() doesn't flag bad crcs on primary sb
      xfs: skip verification on initial "guess" superblock read
      xfs: limit superblock corruption errors to actual corruption

 MAINTAINERS          |    1 -
 fs/xfs/xfs_iops.c    |   16 ++++++++--------
 fs/xfs/xfs_log_cil.c |   19 +++++++++++++++----
 fs/xfs/xfs_mount.c   |   24 ++++++++++++++++--------
 fs/xfs/xfs_sb.c      |   10 ++++------
 5 files changed, 43 insertions(+), 27 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

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

             reply	other threads:[~2014-02-21 22:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 22:59 Dave Chinner [this message]
2014-02-22 16:29 ` [GIT PULL] xfs: fixes for 3.14-rc3 Linus Torvalds

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=20140221225943.GR13647@dastard \
    --to=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox