From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201453] Bug 1640090 - [xfstests xfs/490]: xfs_db print a bad (negative number) as agi freecount
Date: Thu, 18 Oct 2018 01:41:55 +0000 [thread overview]
Message-ID: <bug-201453-201763-LL35Q14HnV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201453-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201453
--- Comment #2 from Dave Chinner (david@fromorbit.com) ---
On Wed, Oct 17, 2018 at 11:20:42AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> # _scratch_xfs_get_metadata_field "recs[1].freecount" "agi 0" "addr root"
> -197
> ]# xfs_db -c "agi 0" -c "addr root" -c "print recs[1]" /dev/loop1
> recs[1] = [startino,holemask,count,freecount,free]
> 1:[128,0,64,-197,0xffffffffffffffe0]
.....
> And it's not reproducible on x86_64:
> # xfs_db -c "agi 0" -c "addr root" -c "print recs[1]" /dev/loop1
> recs[1] = [startino,holemask,count,freecount,free]
> 1:[128,0,64,59,0xffffffffffffffe0]
-197 = -(256 - 59)
This looks like a sign extension problem in the xfs_db code. s390 is
a big endian system, right?
Cheers,
Dave.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-10-18 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 11:20 [Bug 201453] New: Bug 1640090 - [xfstests xfs/490]: xfs_db print a bad (negative number) as agi freecount bugzilla-daemon
2018-10-17 17:49 ` [Bug 201453] " bugzilla-daemon
2018-10-18 1:41 ` [Bug 201453] New: " Dave Chinner
2018-10-18 1:41 ` bugzilla-daemon [this message]
2018-10-18 1:50 ` [Bug 201453] " bugzilla-daemon
2018-10-18 6:25 ` bugzilla-daemon
2018-10-24 20:10 ` bugzilla-daemon
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=bug-201453-201763-LL35Q14HnV@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.