linux-kernel - Re: [build bug] nf_nat_proto_sctp.c:(.text+0x6d173): undefined reference to `crc32c

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, 20 Apr 2008 23:53:54 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mingo@...e.hu
Cc:	linville@...driver.com, tomas.winkler@...el.com,
	linux-kernel@...r.kernel.org, kaber@...sh.net,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
	mabbas@...ux.intel.com, ischram@...enet.be, rjw@...k.pl
Subject: Re: [build bug] nf_nat_proto_sctp.c:(.text+0x6d173): undefined
 reference to `crc32c_le'

From: Ingo Molnar <mingo@...e.hu>
Date: Mon, 21 Apr 2008 08:22:44 +0200

>   net/built-in.o: In function `sctp_manip_pkt':
>   nf_nat_proto_sctp.c:(.text+0x6d173): undefined reference to `crc32c_le'
>   nf_nat_proto_sctp.c:(.text+0x6d180): undefined reference to `crc32c_le'
>   nf_nat_proto_sctp.c:(.text+0x6d196): undefined reference to `crc32c_le'
>   nf_nat_proto_sctp.c:(.text+0x6d1c6): undefined reference to `crc32c_le'
> 
>   http://redhat.com/~mingo/misc/config-Mon_Apr_21_01_52_14_CEST_2008.bad

Thanks for your report Ingo.

Patrick, I'm not so sure how to fix this, or even what's wrong.

NF_NAT_PROTO_SCTP does a proper select on LIBCRC32C, but somehow
NF_NAT_PROTO_SCTP=y and LIBCRC32C=m.

I notice that IP_SCTP=m in this config.  So perhaps the issue is the
case where two features do a select on an infrastructure config
option.  Maybe whoever does the last 'select' gets to decide if the
option gets set to 'y' or 'm'?

It's just a guess, as I still for the life of me can't figure out
how these dependencies get sorted by the kbuild system in situations
like this.

--
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/