linux-kernel - df486a25900 broke arm/mx1_defconfig and probably more

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-next>] [day] [month] [year] [list]

Message-ID: <20100825084912.GA10293@pengutronix.de>
Date:	Wed, 25 Aug 2010 10:49:12 +0200
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>,
	Trond Myklebust <Trond.Myklebust@...app.com>
Cc:	linux-kernel@...r.kernel.org,
	"J. Bruce Fields" <bfields@...ldses.org>
Subject: df486a25900 broke arm/mx1_defconfig and probably more

Hello,

trying to compile mx1_defconfig ends in:

	  LD      .tmp_vmlinux1
	fs/built-in.o: In function `nfs_callback_authenticate':
	compr_zlib.c:(.text+0x7d044): undefined reference to `svc_gss_principal'
	make[2]: *** [.tmp_vmlinux1] Error 1
	make[1]: *** [sub-make] Error 2
	make: *** [all] Error 2
	make: Leaving directory `/ptx/work/octopus/WORK_2_A/ukl/kbuild/imxdefconfigs/mx1'

bisecting yields

	df486a2 (NFS: Fix the selection of security flavours in Kconfig)

as first bad commit.

	$ grep -E -e '(NFS|SUNRPC_GSS|CRYPTO|RPCSEC)' .config
	# CONFIG_USB_FUNCTIONFS is not set
	CONFIG_NFS_FS=y
	CONFIG_NFS_V3=y
	# CONFIG_NFS_V3_ACL is not set
	CONFIG_NFS_V4=y
	# CONFIG_NFS_V4_1 is not set
	CONFIG_ROOT_NFS=y
	# CONFIG_NFSD is not set
	CONFIG_NFS_COMMON=y
	# CONFIG_RPCSEC_GSS_SPKM3 is not set
	# CONFIG_CRYPTO is not set

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
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/