All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sami Tolvanen <samitolvanen@google.com>,
	bpf@vger.kernel.org, Puranjay Mohan <puranjay@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>
Cc: oe-kbuild-all@lists.linux.dev,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Maxwell Bland <mbland@motorola.com>,
	Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH bpf-next v11 2/3] cfi: Move BPF CFI types and helpers to generic code
Date: Mon, 21 Jul 2025 09:25:53 +0800	[thread overview]
Message-ID: <202507210919.wPRFLcKb-lkp@intel.com> (raw)
In-Reply-To: <20250718223345.1075521-7-samitolvanen@google.com>

Hi Sami,

kernel test robot noticed the following build errors:

[auto build test ERROR on 0ee30d937c147fc14c4b49535181d437cd2fde7a]

url:    https://github.com/intel-lab-lkp/linux/commits/Sami-Tolvanen/cfi-add-C-CFI-type-macro/20250719-063535
base:   0ee30d937c147fc14c4b49535181d437cd2fde7a
patch link:    https://lore.kernel.org/r/20250718223345.1075521-7-samitolvanen%40google.com
patch subject: [PATCH bpf-next v11 2/3] cfi: Move BPF CFI types and helpers to generic code
config: arm-randconfig-r072-20250721 (https://download.01.org/0day-ci/archive/20250721/202507210919.wPRFLcKb-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 16534d19bf50bde879a83f0ae62875e2c5120e64)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250721/202507210919.wPRFLcKb-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/202507210919.wPRFLcKb-lkp@intel.com/

All errors (new ones prefixed by >>):

>> <inline asm>:2:41: error: expected '%<type>' or "<type>"
       2 |         .pushsection    .data..ro_after_init,"aw",@progbits     
         |                                                   ^
>> <inline asm>:3:21: error: expected STT_<TYPE_IN_UPPER_CASE>, '#<type>', '%<type>' or "<type>"
       3 |         .type   cfi_bpf_hash,@object                            
         |                              ^
>> <inline asm>:9:19: error: .popsection without corresponding .pushsection
       9 |         .popsection                                             
         |                                                                 ^
   <inline asm>:10:41: error: expected '%<type>' or "<type>"
      10 |         .pushsection    .data..ro_after_init,"aw",@progbits     
         |                                                   ^
   <inline asm>:11:29: error: expected STT_<TYPE_IN_UPPER_CASE>, '#<type>', '%<type>' or "<type>"
      11 |         .type   cfi_bpf_subprog_hash,@object                            
         |                                      ^
   <inline asm>:17:19: error: .popsection without corresponding .pushsection
      17 |         .popsection                                             
         |                                                                 ^
   6 errors generated.

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

  parent reply	other threads:[~2025-07-21  1:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 22:33 [PATCH bpf-next v11 0/3] Support kCFI + BPF on arm64 Sami Tolvanen
2025-07-18 22:33 ` [PATCH bpf-next v11 1/3] cfi: add C CFI type macro Sami Tolvanen
2025-07-18 22:33 ` [PATCH bpf-next v11 2/3] cfi: Move BPF CFI types and helpers to generic code Sami Tolvanen
2025-07-19 23:32   ` kernel test robot
2025-07-21  1:25   ` kernel test robot [this message]
2025-07-21 14:33   ` Will Deacon
2025-07-18 22:33 ` [PATCH bpf-next v11 3/3] arm64/cfi,bpf: Support kCFI + BPF on arm64 Sami Tolvanen

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=202507210919.wPRFLcKb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=daniel@iogearbox.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mbland@motorola.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=puranjay@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=will@kernel.org \
    /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.