linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Petr Tesarik" <petrtesarik@huaweicloud.com>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"David Kaplan" <david.kaplan@amd.com>,
	"Larry Dewey" <larry.dewey@amd.com>,
	"Elena Reshetova" <elena.reshetova@intel.com>,
	"Carlos Bilbao" <carlos.bilbao@amd.com>,
	"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Petr Mladek" <pmladek@suse.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Eric DeVolder" <eric.devolder@oracle.com>,
	"Marc Aurèle La France" <tsi@tuyoix.net>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	"Nhat Pham" <nphamcs@gmail.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Christian Brauner (Microsoft)" <brauner@kernel.org>,
	"Douglas Anderson" <dianders@chromium.org>,
	"Luis Chamberlain" <mcgrof@kernel.org>,
	"Guenter Roeck" <groeck@chromium.org>,
	"Mike Christie" <michael.christie@oracle.com>,
	"Kent Overstreet" <kent.overstreet@linux.dev>,
	"Maninder Singh" <maninder1.s@samsung.com>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Roberto Sassu <roberto.sassu@huaweicloud.com>,
	petr@tesarici.cz,
	Petr Tesarik <petr.tesarik1@huawei-partners.com>
Subject: Re: [PATCH v1 4/5] sbm: SandBox Mode KUnit test suite
Date: Fri, 16 Feb 2024 03:14:44 +0800	[thread overview]
Message-ID: <202402160357.4hi1ecdG-lkp@intel.com> (raw)
In-Reply-To: <20240214113035.2117-5-petrtesarik@huaweicloud.com>

Hi Petr,

kernel test robot noticed the following build errors:

[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on linus/master v6.8-rc4 next-20240215]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Petr-Tesarik/sbm-SandBox-Mode-core-data-types-and-functions/20240214-193528
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20240214113035.2117-5-petrtesarik%40huaweicloud.com
patch subject: [PATCH v1 4/5] sbm: SandBox Mode KUnit test suite
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20240216/202402160357.4hi1ecdG-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 1c10821022f1799452065fb57474e894e2562b7f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240216/202402160357.4hi1ecdG-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202402160357.4hi1ecdG-lkp@intel.com/

All errors (new ones prefixed by >>):

>> kernel/sbm_test.c:648:25: error: use of undeclared identifier 'current_stack_pointer'
     648 |         unsigned long old_sp = current_stack_pointer;
         |                                ^
   kernel/sbm_test.c:651:2: error: use of undeclared identifier 'current_stack_pointer'
     651 |         current_stack_pointer = (unsigned long)end_of_stack(current);
         |         ^
   kernel/sbm_test.c:654:2: error: use of undeclared identifier 'current_stack_pointer'
     654 |         current_stack_pointer = old_sp;
         |         ^
   3 errors generated.


vim +/current_stack_pointer +648 kernel/sbm_test.c

   645	
   646	static SBM_DEFINE_FUNC(stack_overflow)
   647	{
 > 648		unsigned long old_sp = current_stack_pointer;
   649		int err;
   650	
   651		current_stack_pointer = (unsigned long)end_of_stack(current);
   652		barrier();
   653		err = kaboom();
   654		current_stack_pointer = old_sp;
   655		return err;
   656	}
   657	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


       reply	other threads:[~2024-02-15 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240214113035.2117-5-petrtesarik@huaweicloud.com>
2024-02-15 19:14 ` kernel test robot [this message]
2024-02-16  1:53 ` kernel test robot

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=202402160357.4hi1ecdG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=carlos.bilbao@amd.com \
    --cc=corbet@lwn.net \
    --cc=david.kaplan@amd.com \
    --cc=dianders@chromium.org \
    --cc=elena.reshetova@intel.com \
    --cc=eric.devolder@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=gustavoars@kernel.org \
    --cc=kent.overstreet@linux.dev \
    --cc=larry.dewey@amd.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=maninder1.s@samsung.com \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=michael.christie@oracle.com \
    --cc=nphamcs@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paulmck@kernel.org \
    --cc=petr.tesarik1@huawei-partners.com \
    --cc=petr@tesarici.cz \
    --cc=petrtesarik@huaweicloud.com \
    --cc=pmladek@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=roberto.sassu@huaweicloud.com \
    --cc=tsi@tuyoix.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox