public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: David Chinner <dgc@sgi.com>,
	"bnaujok@sgi.com via BugWorks" <bnaujok@sgi.com>,
	xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>,
	asg-qa <asgqa@sgi.com>
Subject: Re: REVIEW XFSQA test out xfs_attr_shortform_bytesfit attr2/attr1 fix
Date: Mon, 14 Apr 2008 13:22:29 +1000	[thread overview]
Message-ID: <20080414032229.GV103491721@sgi.com> (raw)
In-Reply-To: <4802B4E8.3070807@sgi.com>

On Mon, Apr 14, 2008 at 11:35:36AM +1000, Timothy Shimmin wrote:
> Hi Dave and Barry,
> 
> David Chinner wrote:
> >On Wed, Apr 09, 2008 at 06:10:36PM +1000, Timothy Shimmin wrote:
> >>Hi there,
> >>
> >>A test to test out Eric's fix for xfs_attr_shortform_bytesfit
> >>bug when going from attr2 to attr1.
> >>
> >>With TOT kernel, without patch, one can see the corrupted inline
> >>dirents. With patch, all is well.
> >>
> >>The 186.out _should_ be output'ing ATTR2 for the db version
> >>command but I'm awaiting Barry's xfsprogs checkin to fix that one -
> >>and then I will regenerate it.
> >
> >Really? I'm seeing it fail with ATTR2 in the xfs_db output...
> >
> That's what I used to see until I updated to TOT kernel.
> That's weird.

It's likely due to Eric's change to make sb_badfeatures2 =
sb_features2. That will make userspace pick up the attr2 feature
properly regardless of where it is. Perhaps xfs_db is b0rked
w.r.t. reporting attr vs attr2....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  parent reply	other threads:[~2008-04-14  3:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  8:10 REVIEW XFSQA test out xfs_attr_shortform_bytesfit attr2/attr1 fix Timothy Shimmin
2008-04-10  5:36 ` David Chinner
2008-04-14  1:35   ` Timothy Shimmin
2008-04-14  1:46     ` Barry Naujok
2008-04-14  3:22     ` David Chinner [this message]
2008-04-14  3:56       ` Timothy Shimmin
2008-04-14  4:23         ` Timothy Shimmin

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=20080414032229.GV103491721@sgi.com \
    --to=dgc@sgi.com \
    --cc=asgqa@sgi.com \
    --cc=bnaujok@sgi.com \
    --cc=tes@sgi.com \
    --cc=xfs-dev@sgi.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