Re: WARNING in ieee802154_get_llsec_params

2021-03-04 Thread syzbot
syzbot has bisected this issue to:

commit b60673c4c418bef7550d02faf53c34fbfeb366bf
Author: Jakub Kicinski 
Date:   Tue Mar 3 05:05:15 2020 +

nl802154: add missing attribute validation for dev_type

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=100b11b0d0
start commit:   f5427c24 Add linux-next specific files for 20210304
git tree:   linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=120b11b0d0
console output: https://syzkaller.appspot.com/x/log.txt?x=140b11b0d0
kernel config:  https://syzkaller.appspot.com/x/.config?x=a7876f68bf0bea99
dashboard link: https://syzkaller.appspot.com/bug?extid=cde43a581a8e5f317bc2
syz repro:  https://syzkaller.appspot.com/x/repro.syz?x=124c7b46d0
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1276f5b0d0

Reported-by: syzbot+cde43a581a8e5f317...@syzkaller.appspotmail.com
Fixes: b60673c4c418 ("nl802154: add missing attribute validation for dev_type")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection


Re: WARNING in ieee802154_get_llsec_params

2021-03-04 Thread syzbot
syzbot has found a reproducer for the following issue on:

HEAD commit:f5427c24 Add linux-next specific files for 20210304
git tree:   linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12bb4ff2d0
kernel config:  https://syzkaller.appspot.com/x/.config?x=a7876f68bf0bea99
dashboard link: https://syzkaller.appspot.com/bug?extid=cde43a581a8e5f317bc2
syz repro:  https://syzkaller.appspot.com/x/repro.syz?x=124c7b46d0
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1276f5b0d0

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

[ cut here ]
DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 8406 at kernel/locking/mutex.c:928 __mutex_lock_common 
kernel/locking/mutex.c:928 [inline]
WARNING: CPU: 1 PID: 8406 at kernel/locking/mutex.c:928 
__mutex_lock+0xc0b/0x1120 kernel/locking/mutex.c:1093
Modules linked in:
CPU: 1 PID: 8406 Comm: syz-executor446 Not tainted 
5.12.0-rc1-next-20210304-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 
01/01/2011
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:928 [inline]
RIP: 0010:__mutex_lock+0xc0b/0x1120 kernel/locking/mutex.c:1093
Code: 08 84 d2 0f 85 a3 04 00 00 8b 05 98 77 c0 04 85 c0 0f 85 12 f5 ff ff 48 
c7 c6 00 85 6b 89 48 c7 c7 c0 82 6b 89 e8 ed be bc ff <0f> 0b e9 f8 f4 ff ff 65 
48 8b 1c 25 00 f0 01 00 be 08 00 00 00 48
RSP: 0018:c9000163f258 EFLAGS: 00010282
RAX:  RBX:  RCX: 
RDX: 88801e509c00 RSI: 815bc1b5 RDI: f520002c7e3d
RBP: 8880220e0c90 R08:  R09: 
R10: 815b528e R11:  R12: 
R13: dc00 R14: 8a8a8200 R15: 
FS:  01676300() GS:8880b9d0() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7ffc942cffac CR3: 20f9b000 CR4: 001506e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Call Trace:
 ieee802154_get_llsec_params+0x3f/0x70 net/mac802154/cfg.c:321
 rdev_get_llsec_params net/ieee802154/rdev-ops.h:241 [inline]
 nl802154_get_llsec_params+0xce/0x390 net/ieee802154/nl802154.c:745
 nl802154_send_iface+0x7cf/0xa70 net/ieee802154/nl802154.c:823
 nl802154_get_interface+0xeb/0x230 net/ieee802154/nl802154.c:889
 genl_family_rcv_msg_doit+0x228/0x320 net/netlink/genetlink.c:739
 genl_family_rcv_msg net/netlink/genetlink.c:783 [inline]
 genl_rcv_msg+0x328/0x580 net/netlink/genetlink.c:800
 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2502
 genl_rcv+0x24/0x40 net/netlink/genetlink.c:811
 netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]
 netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338
 netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927
 sock_sendmsg_nosec net/socket.c:654 [inline]
 sock_sendmsg+0xcf/0x120 net/socket.c:674
 sys_sendmsg+0x6e8/0x810 net/socket.c:2350
 ___sys_sendmsg+0xf3/0x170 net/socket.c:2404
 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x440899
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 14 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:7ffe18370df8 EFLAGS: 0246 ORIG_RAX: 002e
RAX: ffda RBX: 000107cf RCX: 00440899
RDX:  RSI: 2300 RDI: 0005
RBP:  R08: 7ffe18370f98 R09: 7ffe18370f98
R10: 7ffe18370f98 R11: 0246 R12: 7ffe18370e0c
R13: 431bde82d7b634db R14: 004ae018 R15: 004004a0



WARNING in ieee802154_get_llsec_params

2021-02-23 Thread syzbot
Hello,

syzbot found the following issue on:

HEAD commit:a99163e9 Merge tag 'devicetree-for-5.12' of git://git.kern..
git tree:   upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=144bedf2d0
kernel config:  https://syzkaller.appspot.com/x/.config?x=7a875029a795d230
dashboard link: https://syzkaller.appspot.com/bug?extid=cde43a581a8e5f317bc2

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

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

DEBUG_LOCKS_WARN_ON(lock->magic != lock)
WARNING: CPU: 1 PID: 11257 at kernel/locking/mutex.c:928 __mutex_lock_common 
kernel/locking/mutex.c:928 [inline]
WARNING: CPU: 1 PID: 11257 at kernel/locking/mutex.c:928 
__mutex_lock+0xc0b/0x1120 kernel/locking/mutex.c:1093
Modules linked in:
CPU: 1 PID: 11257 Comm: syz-executor.1 Not tainted 5.11.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 
01/01/2011
RIP: 0010:__mutex_lock_common kernel/locking/mutex.c:928 [inline]
RIP: 0010:__mutex_lock+0xc0b/0x1120 kernel/locking/mutex.c:1093
Code: 08 84 d2 0f 85 a3 04 00 00 8b 05 b8 7c c2 04 85 c0 0f 85 12 f5 ff ff 48 
c7 c6 00 8c 6b 89 48 c7 c7 c0 89 6b 89 e8 96 eb bc ff <0f> 0b e9 f8 f4 ff ff 65 
48 8b 1c 25 00 f0 01 00 be 08 00 00 00 48
RSP: 0018:c90002697068 EFLAGS: 00010286
RAX:  RBX:  RCX: 
RDX: 0004 RSI: 815be2a5 RDI: f520004d2dff
RBP: 8880125b8c50 R08:  R09: 
R10: 815b74be R11:  R12: 
R13: dc00 R14: 8a898fa0 R15: 
FS:  7f12c496b700() GS:8880b9d0() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 0053e038 CR3: 2947b000 CR4: 00350ee0
Call Trace:
 ieee802154_get_llsec_params+0x3f/0x70 net/mac802154/cfg.c:321
 rdev_get_llsec_params net/ieee802154/rdev-ops.h:241 [inline]
 nl802154_get_llsec_params+0xce/0x390 net/ieee802154/nl802154.c:745
 nl802154_send_iface+0x7cf/0xa70 net/ieee802154/nl802154.c:823
 nl802154_dump_interface+0x294/0x490 net/ieee802154/nl802154.c:860
 genl_lock_dumpit+0x60/0x90 net/netlink/genetlink.c:623
 netlink_dump+0x4b9/0xb70 net/netlink/af_netlink.c:2276
 __netlink_dump_start+0x642/0x900 net/netlink/af_netlink.c:2381
 genl_family_rcv_msg_dumpit+0x2af/0x310 net/netlink/genetlink.c:686
 genl_family_rcv_msg net/netlink/genetlink.c:780 [inline]
 genl_rcv_msg+0x434/0x580 net/netlink/genetlink.c:800
 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2502
 genl_rcv+0x24/0x40 net/netlink/genetlink.c:811
 netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline]
 netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338
 netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927
 sock_sendmsg_nosec net/socket.c:652 [inline]
 sock_sendmsg+0xcf/0x120 net/socket.c:672
 sys_sendmsg+0x6e8/0x810 net/socket.c:2348
 ___sys_sendmsg+0xf3/0x170 net/socket.c:2402
 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2435
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x465ef9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:7f12c496b188 EFLAGS: 0246 ORIG_RAX: 002e
RAX: ffda RBX: 0056bf60 RCX: 00465ef9
RDX:  RSI: 2140 RDI: 0004
RBP: 004bcd1c R08:  R09: 
R10:  R11: 0246 R12: 0056bf60
R13: 7b9a9dcf R14: 7f12c496b300 R15: 00022000


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

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