linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>, <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, 6 Aug 2025 16:35:48 +0800	[thread overview]
Message-ID: <aJMT5DsFlOL6V+Nv@xsang-OptiPlex-9020> (raw)
In-Reply-To: <87qzxoeuav.ffs@tglx>

On Wed, Aug 06, 2025 at 10:19:36AM +0200, Thomas Gleixner wrote:
> Oliver!
> 
> On Wed, Aug 06 2025 at 16:01, Oliver Sang wrote:
> > On Thu, Jul 31, 2025 at 04:03:01PM +0200, Thomas Gleixner wrote:
> >> On Thu, Jul 31 2025 at 14:34, Thomas Gleixner wrote:
> >> > Either you make the timeout longer or try the following on the kernel
> >> > command line instead of 'ftrace_dump_on_cpu':
> >> 
> >>   instead of 'ftrace_dump_ooops'
> >
> > sorry for late, I just took several-day off.
> 
> I hope you had a good time!
> 
> > attached dmesg FYI.
> 
> Thanks for doing this. Now the buffer is too short and as nothing stops
> the tracer the interesting stuff goes out of sight.
> 
> Can you please apply the patch below and try again?

got it!

just want to confirm, still use below params or need some modification?

trace_event=preemptirq:preempt_disable,preemptirq:preempt_enable ftrace_dump_on_oops=orig_cpu trace_buf_size=100K panic_on_warn=1


> 
> Thanks,
> 
>         tglx
> ---
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -5850,6 +5850,8 @@ void preempt_count_sub(int val)
>  	/*
>  	 * Underflow?
>  	 */
> +	if (val > preempt_count())
> +		tracing_off();
>  	if (DEBUG_LOCKS_WARN_ON(val > preempt_count()))
>  		return;
>  	/*


  reply	other threads:[~2025-08-06  8:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  8:46 kernel test robot
2025-07-23 17:22 ` Thomas Gleixner
2025-07-25  9:10   ` Oliver Sang
2025-07-25 15:45     ` Thomas Gleixner
2025-07-29  0:22       ` Oliver Sang
2025-07-29  7:27         ` Thomas Gleixner
2025-07-31  1:40           ` Oliver Sang
2025-07-31 12:34             ` Thomas Gleixner
2025-07-31 14:03               ` Thomas Gleixner
2025-08-06  8:01                 ` Oliver Sang
2025-08-06  8:19                   ` Thomas Gleixner
2025-08-06  8:35                     ` Oliver Sang [this message]
2025-08-06 10:39                       ` Thomas Gleixner
2025-08-07  5:21                         ` 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=aJMT5DsFlOL6V+Nv@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --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=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox