public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+00a022dc9979d67df050@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [kernel?] WARNING in enqueue_dl_entity
Date: Sat, 28 Sep 2024 10:15:24 -0700	[thread overview]
Message-ID: <66f839ac.050a0220.aab67.0006.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    13882369ceb9 Merge tag 'hid-for-linus-2024092601' of git:/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17334507980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f1af1dc2e43cf22f
dashboard link: https://syzkaller.appspot.com/bug?extid=00a022dc9979d67df050
compiler:       aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-13882369.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a1a2db588faf/vmlinux-13882369.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a3f594a63d31/Image-13882369.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+00a022dc9979d67df050@syzkaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 34 at kernel/sched/deadline.c:1995 enqueue_dl_entity+0x47c/0x590 kernel/sched/deadline.c:2029
Modules linked in:
CPU: 1 UID: 0 PID: 34 Comm: kcompactd0 Tainted: G    B              6.11.0-syzkaller-10729-g13882369ceb9 #0
Tainted: [B]=BAD_PAGE
Hardware name: linux,dummy-virt (DT)
pstate: a14000c9 (NzCv daIF +PAN -UAO -TCO +DIT -SSBS BTYPE=--)
pc : enqueue_dl_entity+0x47c/0x590 kernel/sched/deadline.c:1995
lr : dl_server_start+0x44/0x12c kernel/sched/deadline.c:1650
sp : ffff800082eab970
x29: ffff800082eab970 x28: f3f0000004f45c00 x27: 0000000000000000
x26: 0000000000000001 x25: 0000000000000000 x24: 0000000000000048
x23: fff000007f8ee800 x22: 0000000000000001 x21: 000000000016e360
x20: 0000000000000001 x19: fff000007f8ef168 x18: 0000000000000000
x17: fff07ffffd1e0000 x16: ffff800080008000 x15: 0000000000000000
x14: 00000000000002e1 x13: 0000000000000377 x12: 0000000000000001
x11: fff000007f8ee880 x10: 0000000000000001 x9 : 0000000000000048
x8 : 0000000000100000 x7 : 0000000000000001 x6 : f3f0000004f45bc0
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000001
Call trace:
 enqueue_dl_entity+0x47c/0x590 kernel/sched/deadline.c:2029
 dl_server_start+0x44/0x12c kernel/sched/deadline.c:1650
 enqueue_task_fair+0x11c/0x3a4 kernel/sched/fair.c:7040
 enqueue_task+0x58/0xbc kernel/sched/core.c:2020
 activate_task+0x68/0x80 kernel/sched/core.c:2062
 attach_task+0x4c/0x74 kernel/sched/fair.c:9631
 attach_tasks kernel/sched/fair.c:9666 [inline]
 sched_balance_rq+0x488/0xc74 kernel/sched/fair.c:11743
 sched_balance_newidle.constprop.0+0x1b0/0x3e4 kernel/sched/fair.c:12785
 pick_next_task_fair+0x50/0x320 kernel/sched/fair.c:8933
 __pick_next_task kernel/sched/core.c:5955 [inline]
 pick_next_task kernel/sched/core.c:6477 [inline]
 __schedule+0x158/0x8e8 kernel/sched/core.c:6629
 __schedule_loop kernel/sched/core.c:6752 [inline]
 schedule+0x34/0x104 kernel/sched/core.c:6767
 schedule_timeout+0x80/0xf4 kernel/time/timer.c:2615
 kcompactd+0x204/0x374 mm/compaction.c:3181
 kthread+0x114/0x118 kernel/kthread.c:389
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
---[ end trace 0000000000000000 ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

             reply	other threads:[~2024-09-28 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28 17:15 syzbot [this message]
2024-11-22 22:48 ` [syzbot] [kernel?] WARNING in enqueue_dl_entity syzbot
2024-11-23  2:10   ` Hillf Danton
2024-11-23  2:12     ` syzbot
2024-12-13 11:03   ` Hillf Danton
2024-12-13 11:32     ` syzbot

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=66f839ac.050a0220.aab67.0006.GAE@google.com \
    --to=syzbot+00a022dc9979d67df050@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzkaller-bugs@googlegroups.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