public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/4] xfsprogs: a couple metadump fixes and sb logging backports
Date: Mon, 23 Feb 2015 10:51:45 -0500	[thread overview]
Message-ID: <1424706709-21594-1-git-send-email-bfoster@redhat.com> (raw)

Hi all,

Patches 1 and 2 are a couple metadump fixes that fell out from playing
around with large block size filesystems (e.g., 64k on ppc64), similar
to the repair patches I had sent recently. Patches 3 and 4 are backports
of a couple of the sb logging rework fixes.

Dave,

I'm not sure what the workflow here is wrt to the sb logging backports.
FWIW, these are the only patches I need on top of the libxfs-3.19-update
branch to get most of the sparse inode bits to backport cleanly. Do you
want to include them in that branch? Otherwise, I'll just keep them in
my sparse inodes branch for now.

Brian

Brian Foster (4):
  metadump: include NULLFSINO check in inode copy code
  metadump: check for non-zero inode alignment
  xfsprogs: remove bitfield based superblock updates
  xfsprogs: consolidate superblock logging functions

 db/metadump.c                    |   3 +-
 db/sb.c                          |   9 +-
 libxfs/support/libxfs_api_defs.h |   2 +-
 libxfs/support/trans.c           |   2 +-
 libxfs/xfs_attr_leaf.c           |   2 +-
 libxfs/xfs_bmap.c                |  14 +-
 libxfs/xfs_sb.c                  | 286 ++++++++++++++-------------------------
 libxfs/xfs_sb.h                  |  11 +-
 libxfs/xfs_shared.h              |  33 ++---
 libxfs/xfs_trans_resv.c          |  14 --
 libxfs/xfs_trans_resv.h          |   1 -
 mdrestore/xfs_mdrestore.c        |   2 +-
 mkfs/proto.c                     |   6 +-
 mkfs/xfs_mkfs.c                  |   4 +-
 repair/phase5.c                  |   2 +-
 repair/sb.c                      |   2 +-
 repair/scan.c                    |   2 +-
 17 files changed, 144 insertions(+), 251 deletions(-)

-- 
1.9.3

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

             reply	other threads:[~2015-02-23 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 15:51 Brian Foster [this message]
2015-02-23 15:51 ` [PATCH 1/4] metadump: include NULLFSINO check in inode copy code Brian Foster
2015-02-23 15:51 ` [PATCH 2/4] metadump: check for non-zero inode alignment Brian Foster
2015-02-23 15:51 ` [PATCH 3/4] xfsprogs: remove bitfield based superblock updates Brian Foster
2015-02-23 15:51 ` [PATCH 4/4] xfsprogs: consolidate superblock logging functions Brian Foster
2015-02-23 22:08 ` [PATCH 0/4] xfsprogs: a couple metadump fixes and sb logging backports Dave Chinner

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=1424706709-21594-1-git-send-email-bfoster@redhat.com \
    --to=bfoster@redhat.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