All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+7227d49ef464b1dff36d@syzkaller.appspotmail.com>
To: dakr@kernel.org, driver-core@lists.linux.dev,
	gregkh@linuxfoundation.org,  lenb@kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	 pavel@kernel.org, rafael@kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] [pm?] WARNING in complete_all (3)
Date: Wed, 13 May 2026 09:05:26 -0700	[thread overview]
Message-ID: <6a04a146.050a0220.54aed.0003.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    f2abc305aa93 riscv: Define __riscv_copy_{,vec_}{words,byte..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11732a1f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1cf93e35eaea44b1
dashboard link: https://syzkaller.appspot.com/bug?extid=7227d49ef464b1dff36d
compiler:       riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: riscv64

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-f2abc305.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/94904c75b810/vmlinux-f2abc305.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2195b3067ea1/Image-f2abc305.xz

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

WARNING: [] kernel/sched/completion.c:76 at complete_all+0x1d2/0x24c kernel/sched/completion.c:76, CPU#1: syz-executor/4284
Modules linked in:
CPU: 1 UID: 0 PID: 4284 Comm: syz-executor Tainted: G        W           syzkaller #0 PREEMPT 
Tainted: [W]=WARN
Hardware name: riscv-virtio,qemu (DT)
epc : complete_all+0x1d2/0x24c kernel/sched/completion.c:76
 ra : complete_all+0x1d2/0x24c kernel/sched/completion.c:76
epc : ffffffff802d3be2 ra : ffffffff802d3be2 sp : ffff8f800b147010
 gp : ffffffff8a24a9a0 tp : ffffaf8019989ac0 t0 : 0000000000000000
 t1 : fffff5ef03994000 t2 : ffffffff91623ec8 s0 : ffff8f800b147050
 s1 : ffffaf80339588e0 a0 : ffffaf8019989ac8 a1 : ffffffff86deaee0
 a2 : 0000000000000002 a3 : ffffffff8014e99c a4 : 0000000000000000
 a5 : 0000000000000000 a6 : fffff5ef03994001 a7 : ffffaf801cca0003
 s2 : ffffaf8072c654a8 s3 : ffffaf801998aac0 s4 : ffffffff91623ec0
 s5 : 1ffff5f00672b110 s6 : 0000000000000001 s7 : ffff8f800b1471c0
 s8 : ffff8f800b147200 s9 : 1ffff1f001628e34 s10: ffffaf801978a380
 s11: ffffaf80339580e0 t3 : ffffffff88060bc0 t4 : fffff5ef03994000
 t5 : fffff5ef03994001 t6 : 0000000000000002 ssp : 0000000000000000
status: 0000000200000120 badaddr: ffffffff802d3be2 cause: 0000000000000003
[<ffffffff802d3be2>] complete_all+0x1d2/0x24c kernel/sched/completion.c:76
[<ffffffff82c8ae64>] device_pm_sleep_init+0x8c/0x124 drivers/base/power/main.c:118
[<ffffffff82c32670>] device_pm_init drivers/base/power/power.h:168 [inline]
[<ffffffff82c32670>] device_initialize+0x200/0x4e4 drivers/base/core.c:3167
[<ffffffff8535e4f8>] netdev_register_kobject+0x28/0x32c net/core/net-sysfs.c:2324
[<ffffffff85263dbc>] register_netdevice+0x1374/0x2490 net/core/dev.c:11420
[<ffffffff832ff322>] wg_newlink+0x3aa/0x75c drivers/net/wireguard/device.c:372
[<ffffffff852a7684>] rtnl_newlink_create net/core/rtnetlink.c:3863 [inline]
[<ffffffff852a7684>] __rtnl_newlink net/core/rtnetlink.c:3994 [inline]
[<ffffffff852a7684>] rtnl_newlink+0xd74/0x2054 net/core/rtnetlink.c:4109
[<ffffffff852aa8aa>] rtnetlink_rcv_msg+0x8e2/0xd84 net/core/rtnetlink.c:6995
[<ffffffff8560bc98>] netlink_rcv_skb+0x1e8/0x394 net/netlink/af_netlink.c:2550
[<ffffffff85297852>] rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:7022
[<ffffffff8560a0f6>] netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
[<ffffffff8560a0f6>] netlink_unicast+0x4f6/0x7c0 net/netlink/af_netlink.c:1344
[<ffffffff8560aba0>] netlink_sendmsg+0x7e0/0xd64 net/netlink/af_netlink.c:1894
[<ffffffff8517a596>] sock_sendmsg_nosec net/socket.c:787 [inline]
[<ffffffff8517a596>] __sock_sendmsg+0xca/0x160 net/socket.c:802
[<ffffffff85185400>] __sys_sendto+0x278/0x350 net/socket.c:2265
[<ffffffff85185598>] __do_sys_sendto net/socket.c:2272 [inline]
[<ffffffff85185598>] __se_sys_sendto net/socket.c:2268 [inline]
[<ffffffff85185598>] __riscv_sys_sendto+0xc0/0x158 net/socket.c:2268
[<ffffffff80078f0a>] syscall_handler+0x92/0x114 arch/riscv/include/asm/syscall.h:112
[<ffffffff8648ebf0>] do_trap_ecall_u+0x3dc/0x61c arch/riscv/kernel/traps.c:342
[<ffffffff864b9f62>] handle_exception+0x15e/0x16a arch/riscv/kernel/entry.S:232


---
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:[~2026-05-13 16:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6a04a146.050a0220.54aed.0003.GAE@google.com \
    --to=syzbot+7227d49ef464b1dff36d@syzkaller.appspotmail.com \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.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 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.