From: Eric Sandeen <sandeen@sandeen.net>
To: Jason Detring <detringj@gmail.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Read corruption on ARM
Date: Wed, 27 Feb 2013 22:50:18 -0600 [thread overview]
Message-ID: <512EE20A.7010103@sandeen.net> (raw)
In-Reply-To: <512EDF37.4050802@sandeen.net>
On 2/27/13 10:38 PM, Eric Sandeen wrote:
...
> re-cc'ing xfs list
>
> So I used pahole to look at all structs, objdump -d to disassemble,
> and md5sum'd the results to see what's different.
>
> pi@raspberrypi ~ $ md5sum cross/*.dis cross/*.pahole native/*.dis native/*.pahole
>
> <manual sort>
>
> c0abd80c3bf049db5e1909fd851261cc cross/xfs-O1-g.ko.pahole
> c0abd80c3bf049db5e1909fd851261cc cross/xfs-O2-g.ko.pahole
> c0abd80c3bf049db5e1909fd851261cc cross/xfs-Os-g.ko.pahole
> c0abd80c3bf049db5e1909fd851261cc native/xfs-O1-g.ko.pahole
> c0abd80c3bf049db5e1909fd851261cc native/xfs-O2-g.ko.pahole
> c0abd80c3bf049db5e1909fd851261cc native/xfs-Os-g.ko.pahole
>
> so all structures look identical, good - but:
>
> while disassembly of these two modules match:
>
> d76f6ebf4d8a1b9f786facefbcf16f69 cross/xfs-O1-g.ko.dis
> d76f6ebf4d8a1b9f786facefbcf16f69 native/xfs-O1-g.ko.dis
>
> do you see the problem w/ the cross-compiled xfs-O1-g.ko as well?
>
> the others differ:
>
> 349f3490a49f2ce539c2b058914f64f0 native/xfs-Os-g.ko.dis
> 91c8e8230774808b538c21a83106a5d7 cross/xfs-Os-g.ko.dis
>
> 649338e1b8eeed6a294504fc76a39cb0 native/xfs-O2-g.ko.dis
> e52c2a48277326c313bba76aa0b33ab7 cross/xfs-O2-g.ko.dis
>
> The diff of the disassembly of the others is huge, hard to
> know where to start just yet. Need an objdump mode that only
> shows function-relative addresses or something to cut down
> on the noise.
Could you try the same, to isolate the differences: objdump -d
all of the *.o files for, say, the -O2 build, md5sum & compare,
and see which ones differ?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-28 4:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 21:58 Read corruption on ARM Jason Detring
2013-02-26 22:33 ` Eric Sandeen
2013-02-26 23:25 ` Jason Detring
[not found] ` <512D49E2.40003@sandeen.net>
[not found] ` <CA+AKrqCrphO-eKy0n=70O9hmB3mXttOsKmTdfRnPxgJM3_PAkQ@mail.gmail.com>
2013-02-27 17:00 ` Eric Sandeen
[not found] ` <CA+AKrqDq5xCNQo1X=MeRBq54ka0FGJEV5Rn6OzwY7eBfJ+8Wkw@mail.gmail.com>
2013-02-27 21:10 ` Eric Sandeen
[not found] ` <512E89C2.9000302@sandeen.net>
[not found] ` <CA+AKrqDaY4cgP+EPLepzUOU2jAOygTuj-0xDtOaGf+O0aRZV_g@mail.gmail.com>
[not found] ` <512E903A.2020405@sandeen.net>
[not found] ` <CA+AKrqAv7-5gGj_cNBNj=-nChKPzi+_HZmH=z2UABG9pDOmpBg@mail.gmail.com>
2013-02-28 4:38 ` Eric Sandeen
2013-02-28 4:50 ` Eric Sandeen [this message]
2013-02-28 5:27 ` Eric Sandeen
2013-02-28 21:38 ` Jason Detring
2013-03-01 2:25 ` Dave Chinner
2013-03-01 2:53 ` Eric Sandeen
2013-03-01 4:54 ` Dave Chinner
2013-02-26 22:37 ` Eric Sandeen
2013-02-26 22:51 ` Eric Sandeen
2013-02-26 23:21 ` Jason Detring
2013-02-27 2:16 ` Dave Chinner
2013-02-27 14:48 ` Eric Sandeen
2013-02-27 7:19 ` Stefan Ring
2013-02-27 14:48 ` Eric Sandeen
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=512EE20A.7010103@sandeen.net \
--to=sandeen@sandeen.net \
--cc=detringj@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