mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Jeff Mahoney <jeffm@suse.com>, Al Viro <viro@ftp.linux.org.uk>,
	Andi Kleen <ak@suse.de>,
	reiserfs-dev@namesys.com, sam@ravnborg.org
Subject: Re: reiserfs NET=n build error
Date: Mon, 4 Dec 2006 16:19:06 -0800	[thread overview]
Message-ID: <20061204161906.f3531b75.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20061128114757.8b027341.randy.dunlap@oracle.com>

On Tue, 28 Nov 2006 11:47:57 -0800 Randy Dunlap wrote:

> On Sun, 19 Nov 2006 17:32:11 -0500 Jeff Mahoney wrote:
> 
> > -----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. :(
> 
> Even more:  MD/raid (=m) is broken in this way also.
> It uses csum_partial(), which isn't present (CONFIG_NET=n).
> 
> Kernel: arch/x86_64/boot/bzImage is ready  (#9)
>   Building modules, stage 2.
>   MODPOST 101 modules
> WARNING: "csum_partial" [drivers/md/md-mod.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> 
> CONFIG_MD=y
> CONFIG_BLK_DEV_MD=m
> CONFIG_MD_LINEAR=m
> # CONFIG_MD_RAID0 is not set
> CONFIG_MD_RAID1=m
> # CONFIG_MD_RAID10 is not set
> # CONFIG_MD_RAID456 is not set
> CONFIG_MD_MULTIPATH=m
> # CONFIG_MD_FAULTY is not set
> CONFIG_BLK_DEV_DM=y
> CONFIG_DM_DEBUG=y
> CONFIG_DM_CRYPT=m
> CONFIG_DM_SNAPSHOT=y
> CONFIG_DM_MIRROR=y
> CONFIG_DM_ZERO=m
> CONFIG_DM_MULTIPATH=y
> CONFIG_DM_MULTIPATH_EMC=m
> 
> ---
> ~Randy
> full broken config for MD:
> http://oss.oracle.com/~rdunlap/configs/config-md-csum

Ingo, Neil:

Al has summarized that csum_partial() is arch-specific.
However, drivers/md/md.c uses it.

Does that mean that RAID volumes are not portable across
(some) architectures?

Should md.c use a specific, known, fixed (as in static,
arch-independent) version of csum_partial()?

Will changing now possibly make some existing volumes
non-portable?

Thanks,
---
~Randy

  reply	other threads:[~2006-12-05  0:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19  4:22 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 [this message]
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=20061204161906.f3531b75.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=ak@suse.de \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome