linux-kernel - Re: reiserfs NET=n build error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 19 Nov 2006 15:13:55 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, reiserfs-dev@...esys.com,
	sam@...nborg.org, ak@...e.de, discuss@...-64.org
Subject: Re: reiserfs NET=n build error

On Sat, Nov 18, 2006 at 08:22:06PM -0800, Randy Dunlap wrote:
> With CONFIG_NET=n and REISERFS_FS=m (randconfig), kernel build ends with
> 
> Kernel: arch/x86_64/boot/bzImage is ready  (#15)
>   Building modules, stage 2.
>   MODPOST 137 modules
> WARNING: "csum_partial" [fs/reiserfs/reiserfs.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> 
> on both 2.6.19-rc6 and 2.6.19-rc6-git2.
> 
> Looks like arch/x86_64/lib/lib.a is not being linked into the
> final kernel image for some reason.  lib.a does contain csum_partial.

The bug is in arch/x86_64/lib/Makefile:

The problem is that lib-y objects only get linked into the kernel image 
when they are used in the kernel image.

Therefore, an EXPORT_SYMBOL in a lib-y object is a bug.

> ~Randy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/