linux-kernel - Re: [PATCH 1/4] Add BUG

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:	Mon, 1 Feb 2016 13:33:54 -0700
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	kbuild test robot <lkp@...el.com>
Cc:	kbuild-all@...org, hpa@...or.com, linux-kernel@...r.kernel.org,
	mingo@...hat.com, tglx@...utronix.de, x86@...nel.org
Subject: Re: [PATCH 1/4] Add BUG_XX() debugging options

On 2/1/16, kbuild test robot <lkp@...el.com> wrote:
> Hi Jeffrey,
>
> [auto build test WARNING on v4.5-rc2]
> [also build test WARNING on next-20160201]
> [cannot apply to tip/x86/core]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-BUG_XX-debugging-options/20160202-040506
> config: x86_64-randconfig-x012-201605 (attached as .config)
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
>    In file included from include/linux/bug.h:4:0,
>                     from include/linux/page-flags.h:9,
>                     from kernel/bounds.c:9:
>>> arch/x86/include/asm/bug.h:14:5: warning: "CONFIG_DEBUG_BUG" is not
>>> defined [-Wundef]
>     #if CONFIG_DEBUG_BUG
>         ^
> --
>    In file included from include/linux/bug.h:4:0,
>                     from include/linux/page-flags.h:9,
>                     from kernel/bounds.c:9:
>>> arch/x86/include/asm/bug.h:14:5: warning: "CONFIG_DEBUG_BUG" is not
>>> defined [-Wundef]
>     #if CONFIG_DEBUG_BUG
>         ^
>    In file included from include/linux/bug.h:4:0,
>                     from include/linux/crypto.h:23,
>                     from arch/x86/kernel/asm-offsets.c:8:
>>> arch/x86/include/asm/bug.h:14:5: warning: "CONFIG_DEBUG_BUG" is not
>>> defined [-Wundef]
>     #if CONFIG_DEBUG_BUG
>         ^
>
> vim +/CONFIG_DEBUG_BUG +14 arch/x86/include/asm/bug.h
>
>      1	#ifndef _ASM_X86_BUG_H
>      2	#define _ASM_X86_BUG_H
>      3	
>      4	#define HAVE_ARCH_BUG
>      5	
>      6	#ifdef CONFIG_DEBUG_BUGVERBOSE
>      7	
>      8	#ifdef CONFIG_X86_32
>      9	# define __BUG_C0	"2:\t.long 1b, %c0\n"
>     10	#else
>     11	# define __BUG_C0	"2:\t.long 1b - 2b, %c0 - 2b\n"
>     12	#endif
>     13	
>   > 14	#if CONFIG_DEBUG_BUG
>     15	#define BUG()							\
>     16	do {								\
>     17		asm volatile("int3");					\
>     18		unreachable();						\
>     19	} while (0)
>     20	#else
>     21	#define BUG()							\
>     22	do {								\
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology
> Center
> https://lists.01.org/pipermail/kbuild-all                   Intel
> Corporation
>


I am looking at this one, but I'm not sure what the point is of
running a test to build something where the defines are ignored.  Is
this file off limits to use CONFIG options in the build?

Jeff