From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-mm@kvack.org, ltp@lists.linux.it, oliver.sang@intel.com
Subject: Re: [tip:locking/futex] [futex] 56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c
Date: Wed, 23 Jul 2025 19:22:43 +0200 [thread overview]
Message-ID: <87a54usty4.ffs@tglx> (raw)
In-Reply-To: <202507231021.dcf24373-lkp@intel.com>
On Wed, Jul 23 2025 at 16:46, kernel test robot wrote:
> kernel test robot noticed "BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c" on:
>
> commit: 56180dd20c19e5b0fa34822997a9ac66b517e7b3 ("futex: Use RCU-based per-CPU reference counting instead of rcuref_t")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git locking/futex
>
> the issue (1)(2) happen randomly upon 56180dd20c.
Hmm.
> a255b78d14324f8a 56180dd20c19e5b0fa34822997a
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :50 48% 24:50 dmesg.BUG:scheduling_while_atomic <---- (2)
> :50 48% 24:50 dmesg.BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c <---- (1)
> 50:50 0% 50:50 dmesg.Mem-Info
> 50:50 0% 50:50 dmesg.invoked_oom-killer:gfp_mask=0x
>
>
>
> 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 <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202507231021.dcf24373-lkp@intel.com
>
>
> [ 286.673775][ C97] BUG: sleeping function called from invalid context at kernel/nsproxy.c:233 <---- (1)
> [ 286.673784][ C97] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6748, name: oom03
> [ 286.673787][ C97] preempt_count: 7ffffffe, expected: 0
Ooops. That's a corrupted preempt counter, which has underflown twice.
Can you please enable CONFIG_DEBUG_PREEMPT, so we can see where this
happens?
Thanks,
tglx
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: lkp@intel.com, Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
oliver.sang@intel.com, oe-lkp@lists.linux.dev,
ltp@lists.linux.it
Subject: Re: [LTP] [tip:locking/futex] [futex] 56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c
Date: Wed, 23 Jul 2025 19:22:43 +0200 [thread overview]
Message-ID: <87a54usty4.ffs@tglx> (raw)
In-Reply-To: <202507231021.dcf24373-lkp@intel.com>
On Wed, Jul 23 2025 at 16:46, kernel test robot wrote:
> kernel test robot noticed "BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c" on:
>
> commit: 56180dd20c19e5b0fa34822997a9ac66b517e7b3 ("futex: Use RCU-based per-CPU reference counting instead of rcuref_t")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git locking/futex
>
> the issue (1)(2) happen randomly upon 56180dd20c.
Hmm.
> a255b78d14324f8a 56180dd20c19e5b0fa34822997a
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :50 48% 24:50 dmesg.BUG:scheduling_while_atomic <---- (2)
> :50 48% 24:50 dmesg.BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c <---- (1)
> 50:50 0% 50:50 dmesg.Mem-Info
> 50:50 0% 50:50 dmesg.invoked_oom-killer:gfp_mask=0x
>
>
>
> 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 <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202507231021.dcf24373-lkp@intel.com
>
>
> [ 286.673775][ C97] BUG: sleeping function called from invalid context at kernel/nsproxy.c:233 <---- (1)
> [ 286.673784][ C97] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 6748, name: oom03
> [ 286.673787][ C97] preempt_count: 7ffffffe, expected: 0
Ooops. That's a corrupted preempt counter, which has underflown twice.
Can you please enable CONFIG_DEBUG_PREEMPT, so we can see where this
happens?
Thanks,
tglx
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-07-23 17:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 8:46 [tip:locking/futex] [futex] 56180dd20c: BUG:sleeping_function_called_from_invalid_context_at_kernel/nsproxy.c kernel test robot
2025-07-23 8:46 ` [LTP] " kernel test robot
2025-07-23 17:22 ` Thomas Gleixner [this message]
2025-07-23 17:22 ` Thomas Gleixner
2025-07-25 9:10 ` Oliver Sang
2025-07-25 9:10 ` [LTP] " Oliver Sang
2025-07-25 15:45 ` Thomas Gleixner
2025-07-25 15:45 ` [LTP] " Thomas Gleixner
2025-07-29 0:22 ` Oliver Sang
2025-07-29 0:22 ` [LTP] " Oliver Sang
2025-07-29 7:27 ` Thomas Gleixner
2025-07-29 7:27 ` [LTP] " Thomas Gleixner
2025-07-31 1:40 ` Oliver Sang
2025-07-31 1:40 ` [LTP] " Oliver Sang
2025-07-31 12:34 ` Thomas Gleixner
2025-07-31 12:34 ` [LTP] " Thomas Gleixner
2025-07-31 14:03 ` Thomas Gleixner
2025-07-31 14:03 ` [LTP] " Thomas Gleixner
2025-08-06 8:01 ` Oliver Sang
2025-08-06 8:01 ` [LTP] " Oliver Sang
2025-08-06 8:19 ` Thomas Gleixner
2025-08-06 8:19 ` [LTP] " Thomas Gleixner
2025-08-06 8:35 ` Oliver Sang
2025-08-06 8:35 ` [LTP] " Oliver Sang
2025-08-06 10:39 ` Thomas Gleixner
2025-08-06 10:39 ` [LTP] " Thomas Gleixner
2025-08-07 5:21 ` Oliver Sang
2025-08-07 5:21 ` [LTP] " Oliver Sang
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=87a54usty4.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=x86@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.