From: kernel test robot <lkp@intel.com>
To: David Gow <davidgow@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] um: Fix misaligned stack in stub_exe
Date: Sat, 19 Oct 2024 03:05:32 +0800 [thread overview]
Message-ID: <202410190227.cYsvc9ss-lkp@intel.com> (raw)
In-Reply-To: <20241017231007.1500497-2-davidgow@google.com>
Hi David,
kernel test robot noticed the following build errors:
[auto build test ERROR on uml/next]
[also build test ERROR on next-20241018]
[cannot apply to linus/master v6.12-rc3]
[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/David-Gow/um-Fix-misaligned-stack-in-stub_exe/20241018-071148
base: https://git.kernel.org/pub/scm/linux/kernel/git/uml/linux next
patch link: https://lore.kernel.org/r/20241017231007.1500497-2-davidgow%40google.com
patch subject: [PATCH] um: Fix misaligned stack in stub_exe
config: um-allnoconfig (https://download.01.org/0day-ci/archive/20241019/202410190227.cYsvc9ss-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241019/202410190227.cYsvc9ss-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/202410190227.cYsvc9ss-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/um/kernel/skas/stub_exe.c:84:2: error: non-ASM statement in naked function is not supported
84 | char *alloc;
| ^
arch/um/kernel/skas/stub_exe.c:82:16: note: attribute is here
82 | __attribute__((naked)) void _start(void)
| ^
1 error generated.
vim +84 arch/um/kernel/skas/stub_exe.c
32e8eaf263d9be Benjamin Berg 2024-09-19 81
ae9ffda02a9904 David Gow 2024-10-18 82 __attribute__((naked)) void _start(void)
32e8eaf263d9be Benjamin Berg 2024-09-19 83 {
32e8eaf263d9be Benjamin Berg 2024-09-19 @84 char *alloc;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-10-18 19:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20241017231007.1500497-2-davidgow@google.com>]
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=202410190227.cYsvc9ss-lkp@intel.com \
--to=lkp@intel.com \
--cc=davidgow@google.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox