From: Peter Zijlstra <peterz@infradead.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>,
Ritesh Harjani <ritesh.list@gmail.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
Srikar Dronamraju <srikar@linux.ibm.com>
Subject: Re: [linux-next20260529] kernel BUG at kernel/sched/core.c:7512!
Date: Mon, 1 Jun 2026 11:56:01 +0200 [thread overview]
Message-ID: <20260601095601.GN3102624@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <2f8c3d75-de2c-48bf-bd05-46b816d55c69@linux.ibm.com>
On Mon, Jun 01, 2026 at 02:46:24PM +0530, Shrikanth Hegde wrote:
> Ritesh, Mukesh, Is below possible scenario?
>
> do_page_fault seems to enable irq's in the interrupt handler?
> is that expected? if so, one might see
>
> -- do_page_fault (enter kernel mode)
> -- enables interrupts
> -- gets interrupt - Sets need_resched.
> -- irqentry_exit - Sees it is kernel mode. Just checks preempt count
> and calls preempt_schedule_irq, which catches both
> preempt_count and !irqs_disabled. Hence the panic?
>
> Should do_page_fault do preempt_disable when it enables the interrupts?
No, it is expected for page-fault to be able to schedule. Specifically,
it must be able to sleep to support loading pages from disk.
Please check the value of preempt_count() (does it perchance have
HARDIRQ_OFFSET?). Also, if the fault handler does enable IRQs, it must
also disable them again once done.
Notably, I see ___do_page_fault() do interrupt_cond_loadl_irq_enable(),
but I'm not seeing a local_irq_disable() to match!
next prev parent reply other threads:[~2026-06-01 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 6:41 [linux-next20260529] kernel BUG at kernel/sched/core.c:7512! Venkat Rao Bagalkote
2026-06-01 9:16 ` Shrikanth Hegde
2026-06-01 9:56 ` Peter Zijlstra [this message]
2026-06-02 7:56 ` Shrikanth Hegde
2026-06-02 8:18 ` Peter Zijlstra
2026-06-02 9:56 ` Shrikanth Hegde
2026-06-02 10:03 ` Peter Zijlstra
2026-06-01 13:33 ` Venkat
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=20260601095601.GN3102624@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mchauras@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=venkat88@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox