All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: kernel test robot <lkp@intel.com>, Kees Cook <keescook@chromium.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-kernel@vger.kernel.org
Subject: Re: [kees:for-next/kspp 21/25] drivers/misc/lkdtm/stackleak.c:17:39: error: call to undeclared function 'stackleak_task_low_bound'; ISO C99 and later do not support implicit function declarations
Date: Thu, 5 May 2022 13:45:37 +0100	[thread overview]
Message-ID: <YnPG8dGulGqxMHt6@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <202205050943.HDgeO9iV-lkp@intel.com>

Hi Kees,

I hadn't realised the LKDTM STACKLEAK test could be built with
CONFIG_STACKLEAK=n, and my rework of that depends upon helpers that only exist
when CONFIG_STACKLEAK=y.

IMO the test is nonsensical for CONFIG_STACKLEAK=n, and I reckon we should
either:

a) Not build the stackleak test at all when CONFIG_STACKLEAK=n

b) Have a small stub that just logs that CONFIG_STACKLEAK=n and the test is
   being skipped.

Do you have any preference between the two?

Thanks,
Mark.

On Thu, May 05, 2022 at 09:43:36AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/kspp
> head:   d46ac904fd35edfccc5080818e950d4d3b4697c4
> commit: f4cfacd92972cc440d534b5156df23d0a2136bab [21/25] lkdtm/stackleak: rework boundary management
> config: s390-randconfig-r044-20220502 (https://download.01.org/0day-ci/archive/20220505/202205050943.HDgeO9iV-lkp@intel.com/config)
> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 363b3a645a1e30011cc8da624f13dac5fd915628)
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # install s390 cross compiling tool for clang build
>         # apt-get install binutils-s390x-linux-gnu
>         # https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=f4cfacd92972cc440d534b5156df23d0a2136bab
>         git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
>         git fetch --no-tags kees for-next/kspp
>         git checkout f4cfacd92972cc440d534b5156df23d0a2136bab
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
> >> drivers/misc/lkdtm/stackleak.c:17:39: error: call to undeclared function 'stackleak_task_low_bound'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>            const unsigned long task_stack_low = stackleak_task_low_bound(current);
>                                                 ^
> >> drivers/misc/lkdtm/stackleak.c:18:40: error: call to undeclared function 'stackleak_task_high_bound'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>            const unsigned long task_stack_high = stackleak_task_high_bound(current);
>                                                  ^
>    drivers/misc/lkdtm/stackleak.c:19:22: warning: incompatible pointer to integer conversion initializing 'const unsigned long' with an expression of type 'unsigned long (void)' [-Wint-conversion]
>            const unsigned long current_sp = current_stack_pointer;
>                                ^            ~~~~~~~~~~~~~~~~~~~~~
>    drivers/misc/lkdtm/stackleak.c:20:43: error: no member named 'lowest_stack' in 'struct task_struct'; did you mean 'ret_stack'?
>            const unsigned long lowest_sp = current->lowest_stack;
>                                                     ^~~~~~~~~~~~
>                                                     ret_stack
>    include/linux/sched.h:1365:28: note: 'ret_stack' declared here
>            struct ftrace_ret_stack         *ret_stack;
>                                             ^
>    drivers/misc/lkdtm/stackleak.c:20:22: warning: incompatible pointer to integer conversion initializing 'const unsigned long' with an expression of type 'struct ftrace_ret_stack *' [-Wint-conversion]
>            const unsigned long lowest_sp = current->lowest_stack;
>                                ^           ~~~~~~~~~~~~~~~~~~~~~
>    drivers/misc/lkdtm/stackleak.c:42:16: error: call to undeclared function 'stackleak_find_top_of_poison'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>            poison_high = stackleak_find_top_of_poison(task_stack_low, untracked_high);
>                          ^
>    2 warnings and 4 errors generated.
> 
> 
> vim +/stackleak_task_low_bound +17 drivers/misc/lkdtm/stackleak.c
> 
>     13	
>     14	void lkdtm_STACKLEAK_ERASING(void)
>     15	{
>     16		const unsigned long task_stack_base = (unsigned long)task_stack_page(current);
>   > 17		const unsigned long task_stack_low = stackleak_task_low_bound(current);
>   > 18		const unsigned long task_stack_high = stackleak_task_high_bound(current);
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://01.org/lkp

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: kbuild-all@lists.01.org
Subject: Re: [kees:for-next/kspp 21/25] drivers/misc/lkdtm/stackleak.c:17:39: error: call to undeclared function 'stackleak_task_low_bound'; ISO C99 and later do not support implicit function declarations
Date: Thu, 05 May 2022 13:45:37 +0100	[thread overview]
Message-ID: <YnPG8dGulGqxMHt6@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <202205050943.HDgeO9iV-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 4795 bytes --]

Hi Kees,

I hadn't realised the LKDTM STACKLEAK test could be built with
CONFIG_STACKLEAK=n, and my rework of that depends upon helpers that only exist
when CONFIG_STACKLEAK=y.

IMO the test is nonsensical for CONFIG_STACKLEAK=n, and I reckon we should
either:

a) Not build the stackleak test at all when CONFIG_STACKLEAK=n

b) Have a small stub that just logs that CONFIG_STACKLEAK=n and the test is
   being skipped.

Do you have any preference between the two?

Thanks,
Mark.

On Thu, May 05, 2022 at 09:43:36AM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/kspp
> head:   d46ac904fd35edfccc5080818e950d4d3b4697c4
> commit: f4cfacd92972cc440d534b5156df23d0a2136bab [21/25] lkdtm/stackleak: rework boundary management
> config: s390-randconfig-r044-20220502 (https://download.01.org/0day-ci/archive/20220505/202205050943.HDgeO9iV-lkp(a)intel.com/config)
> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 363b3a645a1e30011cc8da624f13dac5fd915628)
> reproduce (this is a W=1 build):
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # install s390 cross compiling tool for clang build
>         # apt-get install binutils-s390x-linux-gnu
>         # https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=f4cfacd92972cc440d534b5156df23d0a2136bab
>         git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
>         git fetch --no-tags kees for-next/kspp
>         git checkout f4cfacd92972cc440d534b5156df23d0a2136bab
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
> >> drivers/misc/lkdtm/stackleak.c:17:39: error: call to undeclared function 'stackleak_task_low_bound'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>            const unsigned long task_stack_low = stackleak_task_low_bound(current);
>                                                 ^
> >> drivers/misc/lkdtm/stackleak.c:18:40: error: call to undeclared function 'stackleak_task_high_bound'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>            const unsigned long task_stack_high = stackleak_task_high_bound(current);
>                                                  ^
>    drivers/misc/lkdtm/stackleak.c:19:22: warning: incompatible pointer to integer conversion initializing 'const unsigned long' with an expression of type 'unsigned long (void)' [-Wint-conversion]
>            const unsigned long current_sp = current_stack_pointer;
>                                ^            ~~~~~~~~~~~~~~~~~~~~~
>    drivers/misc/lkdtm/stackleak.c:20:43: error: no member named 'lowest_stack' in 'struct task_struct'; did you mean 'ret_stack'?
>            const unsigned long lowest_sp = current->lowest_stack;
>                                                     ^~~~~~~~~~~~
>                                                     ret_stack
>    include/linux/sched.h:1365:28: note: 'ret_stack' declared here
>            struct ftrace_ret_stack         *ret_stack;
>                                             ^
>    drivers/misc/lkdtm/stackleak.c:20:22: warning: incompatible pointer to integer conversion initializing 'const unsigned long' with an expression of type 'struct ftrace_ret_stack *' [-Wint-conversion]
>            const unsigned long lowest_sp = current->lowest_stack;
>                                ^           ~~~~~~~~~~~~~~~~~~~~~
>    drivers/misc/lkdtm/stackleak.c:42:16: error: call to undeclared function 'stackleak_find_top_of_poison'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>            poison_high = stackleak_find_top_of_poison(task_stack_low, untracked_high);
>                          ^
>    2 warnings and 4 errors generated.
> 
> 
> vim +/stackleak_task_low_bound +17 drivers/misc/lkdtm/stackleak.c
> 
>     13	
>     14	void lkdtm_STACKLEAK_ERASING(void)
>     15	{
>     16		const unsigned long task_stack_base = (unsigned long)task_stack_page(current);
>   > 17		const unsigned long task_stack_low = stackleak_task_low_bound(current);
>   > 18		const unsigned long task_stack_high = stackleak_task_high_bound(current);
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://01.org/lkp

  reply	other threads:[~2022-05-05 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05  1:43 [kees:for-next/kspp 21/25] drivers/misc/lkdtm/stackleak.c:17:39: error: call to undeclared function 'stackleak_task_low_bound'; ISO C99 and later do not support implicit function declarations kernel test robot
2022-05-05 12:45 ` Mark Rutland [this message]
2022-05-05 12:45   ` Mark Rutland
2022-05-05 16:25   ` Kees Cook
2022-05-05 16:25     ` Kees Cook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YnPG8dGulGqxMHt6@FVFF77S0Q05N.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.