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  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, 1 Jan 2012 23:45:51 +0000 (UTC)
From:	Thorsten Glaser <tg@...bsd.de>
To:	Jonathan Nieder <jrnieder@...il.com>
cc:	Nicholas Bellinger <nab@...ux-iscsi.org>,
	Greg Ungerer <gerg@...inux.org>, linux-kernel@...r.kernel.org,
	linux-m68k@...r.kernel.org, target-devel@...r.kernel.org
Subject: Re: [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined!
 (and others)

Jonathan Nieder dixit:

>Could you suggest a patch to arch/m68k/Makefile to do that?

No, I patched it in debian/config/m68k/defines instead.

I’d rather know why upstream doesn’t use -ffreestanding on
_all_ architectures. A kernel is _not_ a hosted environment,
and GCC is right to bring in problems like this.

>    Then drop -ffreestanding from the main Makefile because it isn't
>    needed anymore and implies -fno-builtin, which is wrong now.

This is wrong, GCC builtins are only valid on hosted platforms,
not on freestanding platforms. (Nobody prevents GCC from using
a memcpy builtin that uses, say, SSE instructions, which must
not be used inside kernel code, for an example on a better-known
architecture.) A kernel must always be compiled freestanding,
as do bootloaders. At least since the advent of gcc 3.[34].

bye,
//mirabilos
-- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
	-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
--
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/

Powered by blists - more mailing lists