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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 04 Nov 2007 13:27:44 +0100
From:	Thomas Bächler <thomas@...hlinux.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	David Miller <davem@...emloft.net>, mingo@...e.hu, bunk@...nel.org,
	thomas@...hlinux.org, tglx@...utronix.de,
	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: 2.6.24-rc1-82798a1 compile failure (x86_64)

Sam Ravnborg schrieb:
> I'm afraid some people do not realize a whit about what they do.
> So at least we could let kbuild warn about it.
> Something like this:
> 
> $ export CFLAGS=-O3
> $ make AFLAGS=-fisk
> Makefile:540: "Appending $AFLAGS (-fisk) from command line to kernel defined $AFLAGS"
> Makefile:544: "Appending $CFLAGS (-O3) from environment to kernel defined $CFLAGS"
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   CC      arch/x86/kernel/asm-offsets.s
>   GEN     include/asm-x86/asm-offsets.h
>   CALL    scripts/checksyscalls.sh
>   CC      scripts/mod/empty.o

I agree, this is a sane way to do it. Would this patch have been
applied, I would have found the problem within minutes AND I would have
known that the kernel does use my CFLAGS, which I assumed it wouldn't.

Maybe you should prefix the message with a "WARNING: ".


Download attachment "signature.asc" of type "application/pgp-signature" (253 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ