From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f77.google.com (mail-oo1-f77.google.com [209.85.161.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 088A223D28C for ; Sat, 15 Aug 2026 14:36:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786804596; cv=none; b=ZqOtF/Czw1FVH4rjYpUKHyvipHhWXEHjlcMMnrnHadOqvP8rBUvUb8X4AbauOcwqZA9+7E6bWgcVV6D0/MoFLEnPbo/E5lp1jURJU/IfFuRj/BLQkiZDnfHFdU0iyrQjjPAsCU/AFIhtgi79iO6Ftv9MlE93fbHCHcHM/gM8ykw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786804596; c=relaxed/simple; bh=yeMfwt8TpW6rntQaKrxL0q272VFEZ7vD3L+weGB1ISE=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=tbhSe07FNi7UnDD4NgtJjHEivMu6QO7Ms7tmH2ZUieK79GZr2I2+lXxn37ybUJJk2uKSOCRPH7sAFiKqJ1nM1AZUlM5uT9sVpHECKGU8+qRMmc2k3zdOU9PgJZ0bDJsCLhN0F0A+dht3YuqtTYrsIhHIEXKOb5JWOSLSb7rmgJQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.77 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f77.google.com with SMTP id 006d021491bc7-6b0fd43eb15so135170eaf.2 for ; Sat, 15 Aug 2026 07:36:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786804594; x=1787409394; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=rPXscJ+5mamyeE2uVzanZ9pu7JVJBXCzMNjrcLZp4XE=; b=b/wl/X7Ehg0aH8D03o+Szu7eO+J1+nv6Nl7RBt/6jjKKadD36UA9hzUNC/BLlqYdcT 5tiG8fUPVjwTcKtAOleX71fDtOdj8w2CnMwWGUk2TwS9sYqyQL4BtEc89ouLSSUrzh5W kOSXBxiYp3VEwM2volOlFIaTuO0QbLf86bVSMdVHTdvE5XxrUzOCkk4+5jkqdGr9fwiM Ad5D/f0iG6VYe3lw3YD91k7sfj/SFOCtdB7T40srUqbBMCFKzcRoQjttgaXAqqOvxjTv wFjstvcXW/wPtB1xtn3+7wMYnhveRjNY+itb8dsOLGlEXEbfI1d474bAS6UPgO35npIk FxpA== X-Forwarded-Encrypted: i=1; AHgh+RqSEtMhGJysEfJ3s/R9FmyoUMhsjRSaBH7DcRfmAJ7YZNyxuU/0mepvz4wUKXZfHkEGp/6M5qDqQXwKsMk=@vger.kernel.org X-Gm-Message-State: AOJu0YxLrHNwooDei2np+3DV4F8TvFs3re39413jwmohoWXSZNWREFhu +S0Go8//S38pX/CLhXWrdDc5gdk1AbixrjIQHualPZtj3iJ6B3sGm/ahV5bvnb3KR5/3X7atfps gTuqC25D2tIt4/5k/JlN/41z8oCPRsZBpbOV7M3U7j9d6h3ITxBcX3OW6NlE= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:4c81:b0:6ae:46cd:e901 with SMTP id 006d021491bc7-6b0d6259683mr11476847eaf.17.1786804593945; Sat, 15 Aug 2026 07:36:33 -0700 (PDT) Date: Sat, 15 Aug 2026 07:36:33 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a807971.dbb3a75c.20434b.0018.GAE@google.com> Subject: [syzbot] [kernel?] WARNING in futex_pivot_pending From: syzbot To: andrealmeid@igalia.com, dave@stgolabs.net, dvhart@infradead.org, linux-kernel@vger.kernel.org, mingo@redhat.com, peterz@infradead.org, syzkaller-bugs@googlegroups.com, tglx@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: f9054278acf4 Merge branch 'for-next/core' into for-kernelci git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci console output: https://syzkaller.appspot.com/x/log.txt?x=11ee7879580000 kernel config: https://syzkaller.appspot.com/x/.config?x=ccf4bea59f67007 dashboard link: https://syzkaller.appspot.com/bug?extid=9c28ada89c468ad30713 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 userspace arch: arm64 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=163b3132580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d52a9e580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/dbe6df6b5108/disk-f9054278.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/c3892df8a641/vmlinux-f9054278.xz kernel image: https://storage.googleapis.com/syzbot-assets/0a12ddc085ab/Image-f9054278.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+9c28ada89c468ad30713@syzkaller.appspotmail.com ------------[ cut here ]------------ do not call blocking ops when !TASK_RUNNING; state=2 set at [<000000003d62a0c3>] prepare_to_wait_event+0x2e4/0x3ac kernel/sched/wait.c:-1 WARNING: kernel/sched/core.c:9124 at __might_sleep+0xc0/0xdc kernel/sched/core.c:9120, CPU#0: syz.0.17/4920 Modules linked in: CPU: 0 UID: 0 PID: 4920 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026 pstate: 63400005 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc : __might_sleep+0xc0/0xdc kernel/sched/core.c:9120 lr : __might_sleep+0xc0/0xdc kernel/sched/core.c:9120 sp : ffff8000954d7930 x29: ffff8000954d7930 x28: ffff8000805a9ec8 x27: ffff8000954d7a00 x26: 0000000000000000 x25: ffff8000954d7a08 x24: 0000000000000000 x23: ffff700012a9af3c x22: ffff0000c4c716d0 x21: 0000000000000002 x20: ffff8000869ca160 x19: 000000000000026f x18: 00000000ffffffff x17: ffff8000801682f0 x16: ffff800080168534 x15: ffff80008034b12c x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000002 x9 : dd2fee083d5bf500 x8 : dd2fee083d5bf500 x7 : ffff80008048ea5c x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff8000802f8870 x2 : 0000000100000000 x1 : ffff0000c4c70000 x0 : 0000000000000000 Call trace: __might_sleep+0xc0/0xdc kernel/sched/core.c:9120 (P) __mutex_lock_common kernel/locking/mutex.c:623 [inline] __mutex_lock+0xf8/0xf14 kernel/locking/mutex.c:821 mutex_lock_nested+0x24/0x30 kernel/locking/mutex.c:874 class_mutex_constructor include/linux/mutex.h:253 [inline] futex_pivot_pending+0x30/0xa4 kernel/futex/core.c:1789 futex_hash_allocate+0x73c/0xc20 kernel/futex/core.c:1872 futex_hash_prctl+0xd0/0x324 kernel/futex/core.c:2027 __do_sys_prctl kernel/sys.c:2885 [inline] __se_sys_prctl kernel/sys.c:2534 [inline] __arm64_sys_prctl+0x9c0/0x14e8 kernel/sys.c:2534 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:758 el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:777 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:590 irq event stamp: 78 hardirqs last enabled at (77): [] vprintk_store+0x924/0xb94 kernel/printk/printk.c:2385 hardirqs last disabled at (78): [] el1_brk64+0x20/0x54 arch/arm64/kernel/entry-common.c:445 softirqs last enabled at (54): [] local_bh_enable include/linux/bottom_half.h:33 [inline] softirqs last enabled at (54): [] put_cpu_fpsimd_context arch/arm64/kernel/fpsimd.c:251 [inline] softirqs last enabled at (54): [] fpsimd_restore_current_state+0x39c/0x9c8 arch/arm64/kernel/fpsimd.c:1797 softirqs last disabled at (52): [] local_bh_disable include/linux/bottom_half.h:20 [inline] softirqs last disabled at (52): [] get_cpu_fpsimd_context arch/arm64/kernel/fpsimd.c:234 [inline] softirqs last disabled at (52): [] fpsimd_restore_current_state+0x44/0x9c8 arch/arm64/kernel/fpsimd.c:1790 ---[ 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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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