From: kernel test robot <lkp@intel.com>
To: "Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: [linuxppc:merge-test 4/12] arch/powerpc/include/asm/entry-common.h:273:9: error: implicit declaration of function 'irq_soft_mask_set'; did you mean 'irq_soft_mask_return'?
Date: Sat, 05 Sep 2026 01:00:36 +0800 [thread overview]
Message-ID: <202609050027.YHSqD4Y8-lkp@intel.com> (raw)
tree: https://github.com/linuxppc/linux merge-test
head: d6bf5e8fe0cb733d4c9eb332a5537b77956886a2
commit: 11d09e46b796ac14f24ab63de2c0185a307b2054 [4/12] powerpc/entry: Fix irq_soft_mask corruption on replayed interrupt exit
config: powerpc-allnoconfig (https://download.01.org/0day-ci/archive/20260905/202609050027.YHSqD4Y8-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/20260905/202609050027.YHSqD4Y8-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/202609050027.YHSqD4Y8-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/irq-entry-common.h:14,
from arch/powerpc/include/asm/interrupt.h:70,
from arch/powerpc/kernel/irq.c:58:
arch/powerpc/include/asm/entry-common.h: In function 'arch_interrupt_exit_prepare':
>> arch/powerpc/include/asm/entry-common.h:273:9: error: implicit declaration of function 'irq_soft_mask_set'; did you mean 'irq_soft_mask_return'? [-Wimplicit-function-declaration]
273 | irq_soft_mask_set(IRQS_ALL_DISABLED);
| ^~~~~~~~~~~~~~~~~
| irq_soft_mask_return
vim +273 arch/powerpc/include/asm/entry-common.h
245
246 /*
247 * Care should be taken to note that arch_interrupt_exit_prepare and
248 * arch_interrupt_async_exit_prepare do not necessarily return immediately to
249 * regs context (e.g., if regs is usermode, we don't necessarily return to
250 * user mode). Other interrupts might be taken between here and return,
251 * context switch / preemption may occur in the exit path after this, or a
252 * signal may be delivered, etc.
253 *
254 * The real interrupt exit code is platform specific, e.g.,
255 * interrupt_exit_user_prepare / interrupt_exit_kernel_prepare for 64s.
256 *
257 * However arch_interrupt_nmi_exit_prepare does return directly to regs, because
258 * NMIs do not do "exit work" or replay soft-masked interrupts.
259 */
260 static inline void arch_interrupt_exit_prepare(struct pt_regs *regs)
261 {
262 if (user_mode(regs)) {
263 BUG_ON(regs_is_unrecoverable(regs));
264 BUG_ON(regs_irqs_disabled(regs));
265 /*
266 * We don't need to restore AMR on the way back to userspace for KUAP.
267 * AMR can only have been unlocked if we interrupted the kernel.
268 */
269 kuap_assert_locked();
270 }
271
272 /* irqentry_exit expects to be called with interrupts disabled */
> 273 irq_soft_mask_set(IRQS_ALL_DISABLED);
274 }
275
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-04 17:00 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=202609050027.YHSqD4Y8-lkp@intel.com \
--to=lkp@intel.com \
--cc=maddy@linux.ibm.com \
--cc=mkchauras@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sshegde@linux.ibm.com \
/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.