[v6.1] WARNING in timer_wait_running

5 views
Skip to first unread message

syzbot

unread,
Mar 25, 2023, 2:04:51 PM3/25/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e3a87a10f259 Linux 6.1.21
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=125008f5c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b49b0405a60858ed
dashboard link: https://syzkaller.appspot.com/bug?extid=f753162ec6416eb76ec2
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed3d1f3e75e6/disk-e3a87a10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6d8e44c8c75c/vmlinux-e3a87a10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cebe803ea4fa/bzImage-e3a87a10.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4727 at kernel/time/posix-timers.c:849 timer_wait_running+0x1ce/0x200
Modules linked in:
CPU: 0 PID: 4727 Comm: syz-executor.5 Not tainted 6.1.21-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:timer_wait_running+0x1ce/0x200 kernel/time/posix-timers.c:849
Code: 8a e8 c6 c3 ee ff e8 b1 36 f8 ff e8 dc fa ff ff 44 89 f7 4c 89 fe 5b 41 5c 41 5d 41 5e 41 5f 5d e9 27 85 ff ff e8 72 52 0e 00 <0f> 0b e9 5b ff ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 70 fe ff
RSP: 0018:ffffc900032ffd08 EFLAGS: 00010287
RAX: ffffffff817b356e RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc9000ce09000 RSI: 000000000000007a RDI: 000000000000007b
RBP: 0000000000000001 R08: dffffc0000000000 R09: ffffed100f1fecc1
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888078ff65e0
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffc900032ffd80
FS: 00007ffb11229700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000001e495000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
do_timer_settime+0x272/0x330 kernel/time/posix-timers.c:929
__do_sys_timer_settime kernel/time/posix-timers.c:952 [inline]
__se_sys_timer_settime kernel/time/posix-timers.c:938 [inline]
__x64_sys_timer_settime+0x1a2/0x250 kernel/time/posix-timers.c:938
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ffb1048c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffb11229168 EFLAGS: 00000246 ORIG_RAX: 00000000000000df
RAX: ffffffffffffffda RBX: 00007ffb105ac050 RCX: 00007ffb1048c0f9
RDX: 0000000020000080 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007ffb104e7b39 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000200001c0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe6cb9e3ff R14: 00007ffb11229300 R15: 0000000000022000
</TASK>


---
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 syzk...@googlegroups.com.

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

syzbot

unread,
Mar 26, 2023, 10:26:44 AM3/26/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: e3a87a10f259 Linux 6.1.21
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=160b74dec80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b49b0405a60858ed
dashboard link: https://syzkaller.appspot.com/bug?extid=f753162ec6416eb76ec2
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c381dec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15afae51c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed3d1f3e75e6/disk-e3a87a10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6d8e44c8c75c/vmlinux-e3a87a10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cebe803ea4fa/bzImage-e3a87a10.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 7259 at kernel/time/posix-timers.c:849 timer_wait_running+0x1ce/0x200
Modules linked in:
CPU: 1 PID: 7259 Comm: syz-executor667 Not tainted 6.1.21-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:timer_wait_running+0x1ce/0x200 kernel/time/posix-timers.c:849
Code: 8a e8 c6 c3 ee ff e8 b1 36 f8 ff e8 dc fa ff ff 44 89 f7 4c 89 fe 5b 41 5c 41 5d 41 5e 41 5f 5d e9 27 85 ff ff e8 72 52 0e 00 <0f> 0b e9 5b ff ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 70 fe ff
RSP: 0018:ffffc90006067d08 EFLAGS: 00010293
RAX: ffffffff817b356e RBX: 0000000000000000 RCX: ffff888075bb9d40
RDX: 0000000000000000 RSI: ffffffff8aebc5e0 RDI: 0000000000000001
RBP: 0000000000000001 R08: dffffc0000000000 R09: ffffed100f949c05
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807ca4e000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffffc90006067d80
FS: 00007f74d1326700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001008 CR3: 0000000074a6a000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
do_timer_settime+0x272/0x330 kernel/time/posix-timers.c:929
__do_sys_timer_settime kernel/time/posix-timers.c:952 [inline]
__se_sys_timer_settime kernel/time/posix-timers.c:938 [inline]
__x64_sys_timer_settime+0x1a2/0x250 kernel/time/posix-timers.c:938
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f74d13983a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f74d1326208 EFLAGS: 00000246 ORIG_RAX: 00000000000000df
RAX: ffffffffffffffda RBX: 00007f74d1420418 RCX: 00007f74d13983a9
RDX: 0000000020000080 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f74d1420410 R08: 00007f74d1326700 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f74d142041c
R13: 00007ffed1eaa23f R14: 00007f74d1326300 R15: 0000000000022000
</TASK>

syzbot

unread,
Sep 12, 2023, 2:04:47 AM9/12/23
to syzkaller...@googlegroups.com
syzbot suspects this issue could be fixed by backporting the following commit:

commit d772781964415c63759572b917e21c4f7ec08d9f
git tree: upstream
Author: Jakub Kicinski <ku...@kernel.org>
Date: Fri Jan 6 06:33:54 2023 +0000

devlink: bump the instance index directly when iterating

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15971378680000
Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages