Message-ID: <000000000000c0e6af0610274383@google.com>
Date: Tue, 30 Jan 2024 02:31:26 -0800
From: syzbot <syzbot+2c3c83033160c81c9af2@...kaller.appspotmail.com>
To: bmt@...ich.ibm.com, jgg@...pe.ca, leon@...nel.org, 
	linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org, 
	netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [rdma?] WARNING: ODEBUG bug in __init_work (4)

Hello,

syzbot found the following issue on:

HEAD commit:    01af33cc9894 Add linux-next specific files for 20240125
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=111c74f3e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4b73726a6eef71f1
dashboard link: https://syzkaller.appspot.com/bug?extid=2c3c83033160c81c9af2
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bd3f86d4b4a5/disk-01af33cc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/39432e805e81/vmlinux-01af33cc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ebd665cc1f02/bzImage-01af33cc.xz

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

netlink: 'syz-executor.2': attribute type 27 has an invalid length.
netlink: 4 bytes leftover after parsing attributes in process `syz-executor.2'.
------------[ cut here ]------------
ODEBUG: init active (active state 0) object: ffff88802b745128 object type: work_struct hint: siw_netdev_down+0x0/0x210 drivers/infiniband/sw/siw/siw_main.c:87
WARNING: CPU: 1 PID: 31079 at lib/debugobjects.c:514 debug_print_object+0x1a3/0x2b0 lib/debugobjects.c:514
Modules linked in:
CPU: 1 PID: 31079 Comm: syz-executor.2 Not tainted 6.8.0-rc1-next-20240125-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:debug_print_object+0x1a3/0x2b0 lib/debugobjects.c:514
Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 54 48 8b 14 dd c0 d3 4e 8b 41 56 4c 89 e6 48 c7 c7 20 c7 4e 8b e8 3e 95 d4 fc 90 <0f> 0b 90 90 58 83 05 55 9e fe 0a 01 48 83 c4 18 5b 5d 41 5c 41 5d
RSP: 0018:ffffc9000ae3ed88 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffc9000d729000
RDX: 0000000000040000 RSI: ffffffff81504dd6 RDI: 0000000000000001
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: fffffffffffc0828 R12: ffffffff8b4ecd80
R13: ffffffff8aebd9e0 R14: ffffffff8808d330 R15: ffffc9000ae3ee48
FS:  00007f4e39bbd6c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000a030 CR3: 0000000065e5a000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 __debug_object_init+0x28c/0x480 lib/debugobjects.c:653
 __init_work+0x4c/0x60 kernel/workqueue.c:591
 siw_device_goes_down drivers/infiniband/sw/siw/siw_main.c:395 [inline]
 siw_netdev_event+0x24d/0x530 drivers/infiniband/sw/siw/siw_main.c:422
 notifier_call_chain+0xb9/0x3e0 kernel/notifier.c:93
 call_netdevice_notifiers_info+0xbe/0x140 net/core/dev.c:1966
 call_netdevice_notifiers_extack net/core/dev.c:2004 [inline]
 call_netdevice_notifiers net/core/dev.c:2018 [inline]
 __dev_close_many+0xf4/0x310 net/core/dev.c:1504
 __dev_close net/core/dev.c:1542 [inline]
 __dev_change_flags+0x4dc/0x720 net/core/dev.c:8646
 dev_change_flags+0x8f/0x160 net/core/dev.c:8720
 do_setlink+0x1abc/0x40c0 net/core/rtnetlink.c:2903
 rtnl_group_changelink net/core/rtnetlink.c:3452 [inline]
 __rtnl_newlink+0xe11/0x1960 net/core/rtnetlink.c:3711
 rtnl_newlink+0x67/0xa0 net/core/rtnetlink.c:3748
 rtnetlink_rcv_msg+0x3c7/0xe10 net/core/rtnetlink.c:6615
 netlink_rcv_skb+0x16b/0x440 net/netlink/af_netlink.c:2543
 netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]
 netlink_unicast+0x542/0x820 net/netlink/af_netlink.c:1367
 netlink_sendmsg+0x8b8/0xd70 net/netlink/af_netlink.c:1908
 sock_sendmsg_nosec net/socket.c:730 [inline]
 __sock_sendmsg net/socket.c:745 [inline]
 ____sys_sendmsg+0xab5/0xc90 net/socket.c:2584
 ___sys_sendmsg+0x135/0x1e0 net/socket.c:2638
 __sys_sendmsg+0x117/0x1f0 net/socket.c:2667
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7f4e3a87cda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4e39bbd0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f4e3a9ac1f0 RCX: 00007f4e3a87cda9
RDX: 0000000000000000 RSI: 0000000020006440 RDI: 0000000000000007
RBP: 00007f4e3a8c947a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f4e3a9ac1f0 R15: 00007fff46e53798
 </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 syzkaller@...glegroups.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

Powered by blists - more mailing lists