All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	linux-kernel@vger.kernel.org, aubrey.li@linux.intel.com,
	yu.c.chen@intel.com
Subject: Re: [peterz-queue:sched/core] [sched/fair]  420356c350: WARNING:at_kernel/sched/core.c:#__might_sleep
Date: Sat, 17 Aug 2024 11:33:29 +0200	[thread overview]
Message-ID: <20240817093329.GA32430@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <202408161619.9ed8b83e-lkp@intel.com>

On Fri, Aug 16, 2024 at 05:15:12PM +0800, kernel test robot wrote:
> kernel test robot noticed "WARNING:at_kernel/sched/core.c:#__might_sleep" on:
> 
> commit: 420356c3504091f0f6021974389df7c58f365dad ("sched/fair: Implement delayed dequeue")
> https://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git sched/core

> [   86.252370][  T674] ------------[ cut here ]------------
> [ 86.252945][ T674] do not call blocking ops when !TASK_RUNNING; state=1 set at kthread_worker_fn (kernel/kthread.c:?) 
> [ 86.254001][ T674] WARNING: CPU: 1 PID: 674 at kernel/sched/core.c:8469 __might_sleep (kernel/sched/core.c:8465) 

> [ 86.283398][ T674] ? handle_bug (arch/x86/kernel/traps.c:239) 
> [ 86.283995][ T674] ? exc_invalid_op (arch/x86/kernel/traps.c:260) 
> [ 86.284787][ T674] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) 
> [ 86.285682][ T674] ? __might_sleep (kernel/sched/core.c:8465) 
> [ 86.286380][ T674] ? __might_sleep (kernel/sched/core.c:8465) 
> [ 86.287116][ T674] kthread_worker_fn (include/linux/kernel.h:73 include/linux/freezer.h:53 kernel/kthread.c:851) 
> [ 86.287701][ T674] ? kthread_worker_fn (kernel/kthread.c:?) 
> [ 86.288138][ T674] kthread (kernel/kthread.c:391) 
> [ 86.288482][ T674] ? __cfi_kthread_worker_fn (kernel/kthread.c:803) 
> [ 86.288951][ T674] ? __cfi_kthread (kernel/kthread.c:342) 
> [ 86.289560][ T674] ret_from_fork (arch/x86/kernel/process.c:153) 
> [ 86.290162][ T674] ? __cfi_kthread (kernel/kthread.c:342) 
> [ 86.291465][ T674] ret_from_fork_asm (arch/x86/entry/entry_64.S:254) 

AFAICT this is a pre-existing issue. Notably that all transcribes to:

kthread_worker_fn()
  ...
repeat:
  set_current_state(TASK_INTERRUPTIBLE);
  ...
  if (work) { // false
    __set_current_state(TASK_RUNNING);
    ...
  } else if (!freezing(current)) // false -- we are freezing
    schedule();

  // so state really is still TASK_INTERRUPTIBLE here
  try_to_freeze()
    might_sleep() <--- boom, per the above.


  reply	other threads:[~2024-08-17  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  9:15 [peterz-queue:sched/core] [sched/fair] 420356c350: WARNING:at_kernel/sched/core.c:#__might_sleep kernel test robot
2024-08-17  9:33 ` Peter Zijlstra [this message]
2024-08-19  4:44   ` Chen Yu
2024-08-19  8:40     ` Oliver Sang
2024-08-22 15:49     ` Peter Zijlstra
2024-08-26  8:25       ` Chen Yu
2024-08-27  9:40         ` Chen Yu

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=20240817093329.GA32430@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=aubrey.li@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=yu.c.chen@intel.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.