LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linuxppc-dev@lists.ozlabs.org,
	"Madhavan Srinivasan" <maddy@linux.ibm.com>,
	"Michal Suchánek " <msuchanek@suse.de>
Subject: [powerpc:fixes-test 12/12] arch/powerpc/include/asm/ptrace.h:241:33: error: implicit declaration of function 'BIT'
Date: Sat, 11 Jul 2026 01:46:54 +0800	[thread overview]
Message-ID: <202607110141.nUx3NKwu-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git fixes-test
head:   afc2830892a128a13a65f677271a0a48aeb61b5e
commit: afc2830892a128a13a65f677271a0a48aeb61b5e [12/12] powerpc/syscall: Fix syscall skip handling for seccomp and ptrace
config: powerpc-allnoconfig (https://download.01.org/0day-ci/archive/20260711/202607110141.nUx3NKwu-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260711/202607110141.nUx3NKwu-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/202607110141.nUx3NKwu-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from arch/powerpc/include/asm/user.h:5,
                    from include/linux/user.h:1,
                    from include/linux/elfcore.h:5,
                    from include/linux/vmcore_info.h:6,
                    from include/linux/kexec.h:18,
                    from include/linux/crash_dump.h:5,
                    from drivers/of/fdt.c:11:
   arch/powerpc/include/asm/ptrace.h: In function 'set_syscall_entry_ret':
>> arch/powerpc/include/asm/ptrace.h:241:33: error: implicit declaration of function 'BIT' [-Wimplicit-function-declaration]
     241 | #define SYSCALL_ENTRY_RET_SET   BIT(0)
         |                                 ^~~
   arch/powerpc/include/asm/ptrace.h:245:30: note: in expansion of macro 'SYSCALL_ENTRY_RET_SET'
     245 |         regs->entry_flags |= SYSCALL_ENTRY_RET_SET;
         |                              ^~~~~~~~~~~~~~~~~~~~~


vim +/BIT +241 arch/powerpc/include/asm/ptrace.h

   228	
   229	#define force_successful_syscall_return()   \
   230		do { \
   231			set_thread_flag(TIF_NOERROR); \
   232		} while(0)
   233	
   234	#define current_pt_regs() \
   235		((struct pt_regs *)((unsigned long)task_stack_page(current) + THREAD_SIZE) - 1)
   236	
   237	/*
   238	 * SYSCALL_ENTRY_RET_SET: seccomp or ptrace called syscall_set_return_value()
   239	 * and wants the syscall skipped; regs->gpr[3] already holds the return value.
   240	 */
 > 241	#define SYSCALL_ENTRY_RET_SET	BIT(0)
   242	

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


                 reply	other threads:[~2026-07-10 17:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202607110141.nUx3NKwu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mkchauras@gmail.com \
    --cc=msuchanek@suse.de \
    --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