linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Michael L. Semon" <mlsemon35@gmail.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [NOISE] merge window blues, XFS broken
Date: Wed, 12 Feb 2014 12:55:46 +1100	[thread overview]
Message-ID: <20140212015546.GP13647@dastard> (raw)
In-Reply-To: <alpine.LNX.2.11.1402111853440.12612@bpserver.ds>

On Tue, Feb 11, 2014 at 07:15:47PM -0500, Michael L. Semon wrote:
> On Tue, 28 Jan 2014, Dave Chinner wrote:
> >Ok, so xfs_inode_item_format+0x4a is inside the very first call to
> >preapre the ilf structure. That tells us that the initial
> >xfs_log_vec/xfs_log_iovec array are resulting in an unaligned
> >buffer.
> >
> >Can you try the patch below, Michael?
> 
> This patch still works fine.  This reply is only in hopes that the
> patch doesn't get lost for being in a subthread of a [NOISE] post.
> I'm having to use this patch quite a bit in order to use XFS at all
> on 32-bit x86.

It's in xfs-fixes-for-3.14-rc3 anf for-next right now. It'll go
upstream in the next couple of days.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

      reply	other threads:[~2014-02-12  1:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 19:35 [NOISE] merge window blues, XFS broken Michael L. Semon
2014-01-27  1:56 ` Dave Chinner
2014-01-27  7:41   ` Christoph Hellwig
2014-01-27  9:46   ` Michael L. Semon
2014-01-27 23:30     ` Dave Chinner
2014-01-28  8:22       ` Michael L. Semon
2014-01-28  9:55         ` Dave Chinner
2014-01-29 22:31           ` Michael L. Semon
2014-02-12  0:15           ` Michael L. Semon
2014-02-12  1:55             ` 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=20140212015546.GP13647@dastard \
    --to=david@fromorbit.com \
    --cc=mlsemon35@gmail.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;
as well as URLs for NNTP newsgroup(s).