From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/4] xfsprogs: a couple metadump fixes and sb logging backports
Date: Tue, 24 Feb 2015 09:08:54 +1100 [thread overview]
Message-ID: <20150223220854.GW4251@dastard> (raw)
In-Reply-To: <1424706709-21594-1-git-send-email-bfoster@redhat.com>
On Mon, Feb 23, 2015 at 10:51:45AM -0500, Brian Foster wrote:
> 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.
I'll pull the fixes into the current branch - we've probably got
enough fixes queued up now to justify a 3.2.3 release.
> 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.
What needs to happen is a full sync up to 4.0-rc1 - the libxfs
kernel side is a moving target. Hopefully that's not a huge amount
of work right now - I'll see if I can get it done by the end of the
week.
But, really, the biggest roadblock right now is getting some review
of the major updates and build changes that are in that branch so
we can move it towards a 3.3. release sooner rather than later.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-02-23 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:51 [PATCH 0/4] xfsprogs: a couple metadump fixes and sb logging backports Brian Foster
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 ` Dave Chinner [this message]
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=20150223220854.GW4251@dastard \
--to=david@fromorbit.com \
--cc=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