From: Jeff Mahoney <jeffm@suse.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, Andi Kleen <ak@suse.de>,
lkml <linux-kernel@vger.kernel.org>,
reiserfs-dev@namesys.com, sam@ravnborg.org
Subject: Re: reiserfs NET=n build error
Date: Sun, 19 Nov 2006 17:32:11 -0500 [thread overview]
Message-ID: <4560DB6B.9020601@suse.com> (raw)
In-Reply-To: <20061119205711.GE3078@ftp.linux.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Al Viro wrote:
> On Sun, Nov 19, 2006 at 11:04:33AM -0800, Randy Dunlap wrote:
>> Andi Kleen wrote:
>>>>> I would copy a relatively simple C implementation, like
>>>>> arch/h8300/lib/checksum.c
>>>> As long as the h8300 version has the same output as the x86 version.
>>> The trouble is that the different architecture have different output
>>> for csum_partial. So you already got a bug when someone wants to move
>>> file systems.
>>>
>>> -Andi
>> That argues for having only one version of it (in a lib.; my preference)
>> -or- Every module having its own local copy/version of it. :(
>
> Wrong. csum_partial() result is defined modulo 0xffff and it's basically
> "whatever's convenient as intermediate for this architecture".
>
> reiserfs use of it is just plain broken. net/* is fine, since all
> final uses are via csum_fold() or equivalents.
>
> Note that reiserfs use is broken in another way: it takes fixed-endian value
> and feeds it to cpu_to_le32(). IOW, even if everything had literally the
> same csum_partial(), the value it shits on disk would be endian-dependent.
Oh great. Even better. :(
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFFYNtqLPWxlyuTD7IRAux8AKCbxW4zX5Q7y8LfPT0FY/W4A8v0PQCggV11
EbMvTGkAb5WXa0f7EgUz5Qk=
=Zm0q
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-11-19 22:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 4:22 reiserfs NET=n build error Randy Dunlap
2006-11-19 5:50 ` Andi Kleen
2006-11-19 17:09 ` Jeff Mahoney
2006-11-19 18:59 ` Andi Kleen
2006-11-19 19:04 ` Randy Dunlap
2006-11-19 20:57 ` Al Viro
2006-11-19 21:02 ` Randy Dunlap
2006-11-19 22:32 ` Jeff Mahoney [this message]
2006-11-28 19:47 ` Randy Dunlap
2006-12-05 0:19 ` Randy Dunlap
2006-12-05 1:20 ` Neil Brown
2006-11-19 20:12 ` Jeff Mahoney
2006-11-19 20:52 ` Al Viro
2006-11-19 14:13 ` Adrian Bunk
2006-11-19 14:53 ` [discuss] " Andi Kleen
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=4560DB6B.9020601@suse.com \
--to=jeffm@suse.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=reiserfs-dev@namesys.com \
--cc=sam@ravnborg.org \
--cc=viro@ftp.linux.org.uk \
/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