From: Jeff Mahoney <jeffm@suse.com>
To: Andi Kleen <ak@suse.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
reiserfs-dev@namesys.com, sam@ravnborg.org,
Al Viro <viro@ftp.linux.org.uk>
Subject: Re: reiserfs NET=n build error
Date: Sun, 19 Nov 2006 15:12:31 -0500 [thread overview]
Message-ID: <4560BAAF.2030202@suse.com> (raw)
In-Reply-To: <200611191959.55969.ak@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
Yeah, Al Viro noticed that about reiserfs earlier this month. The
problem is that there's really no good fix for it. I was under the
impression that csum_partial would be arch-independent and was in asm/
for performance reasons. The comment in asm-x86_64 indicates that's not
the case, but the comment in asm-i386 still doesn't. I developed the
code on i386. Moving forward we can define an arch-independent hash
function for that and accept the old arch-dependent checksums, but
there's still the issue of old kernels not understanding it on any arch.
Kind of a nice shot to the foot considering the work I put into making
reiserfs endian safe in the 2.4 days.
I'm hoping there's a better solution to be found than creating a
checksum verifier that checks all known versions. :(
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFFYLqvLPWxlyuTD7IRAj7RAKCkOHL9EgTrmHSo97xzG5tBxWgzCACgiBcW
uzd/oSwXDHECHPEcIL58xoo=
=udEd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-11-19 20:10 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
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 [this message]
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=4560BAAF.2030202@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