All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e6d0c38bbcbe4d450b6c@syzkaller.appspotmail.com>
To: davem@davemloft.net, johannes.berg@intel.com,
	johannes@sipsolutions.net, kuba@kernel.org, kvalo@codeaurora.org,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, ramonreisfontes@gmail.com,
	syzkaller-bugs@googlegroups.com
Subject: WARNING: ODEBUG bug in ieee80211_ibss_setup_sdata
Date: Thu, 28 Jan 2021 06:29:17 -0800	[thread overview]
Message-ID: <00000000000074fd2305b9f6b6be@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    e1ae4b0b Merge branch 'mtd/fixes' of git://git.kernel.org/..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10bb1c78d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=be33d8015c9de024
dashboard link: https://syzkaller.appspot.com/bug?extid=e6d0c38bbcbe4d450b6c
compiler:       gcc (GCC) 10.1.0-syz 20200507
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10c346b4d00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15a0e944d00000

The issue was bisected to:

commit 7dfd8ac327301f302b03072066c66eb32578e940
Author: Ramon Fontes <ramonreisfontes@gmail.com>
Date:   Thu Oct 10 18:13:07 2019 +0000

    mac80211_hwsim: add support for OCB

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12a22930d00000
final oops:     https://syzkaller.appspot.com/x/report.txt?x=11a22930d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=16a22930d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e6d0c38bbcbe4d450b6c@syzkaller.appspotmail.com
Fixes: 7dfd8ac32730 ("mac80211_hwsim: add support for OCB")

------------[ cut here ]------------
ODEBUG: init active (active state 0) object type: timer_list hint: 0x0
WARNING: CPU: 1 PID: 8473 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Modules linked in:
CPU: 0 PID: 8473 Comm: syz-executor073 Not tainted 5.11.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505
Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd c0 eb 9e 89 4c 89 ee 48 c7 c7 c0 df 9e 89 e8 46 18 f6 04 <0f> 0b 83 05 65 f3 40 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:ffffc900016bf470 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000
RDX: ffff8880149bb780 RSI: ffffffff815b6bc5 RDI: fffff520002d7e80
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff815afd9e R11: 0000000000000000 R12: ffffffff894d8a40
R13: ffffffff899ee4c0 R14: ffffffff8161c7f0 R15: ffffffff8f305280
FS:  00000000018be880(0000) GS:ffff8880b9e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056278b5def48 CR3: 000000001841b000 CR4: 0000000000350ef0
Call Trace:
 __debug_object_init+0x524/0xd10 lib/debugobjects.c:588
 debug_timer_init kernel/time/timer.c:722 [inline]
 debug_init kernel/time/timer.c:770 [inline]
 init_timer_key+0x2d/0x340 kernel/time/timer.c:814
 ieee80211_ibss_setup_sdata+0x34/0x1b0 net/mac80211/ibss.c:1734
 ieee80211_setup_sdata+0xc3a/0xed0 net/mac80211/iface.c:1534
 ieee80211_runtime_change_iftype net/mac80211/iface.c:1636 [inline]
 ieee80211_if_change_type+0x535/0x620 net/mac80211/iface.c:1656
 ieee80211_change_iface+0x26/0x210 net/mac80211/cfg.c:157
 rdev_change_virtual_intf net/wireless/rdev-ops.h:69 [inline]
 cfg80211_change_iface+0x307/0xf10 net/wireless/util.c:1067
 nl80211_set_interface+0x65c/0x8d0 net/wireless/nl80211.c:3839
 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:2494
 genl_rcv+0x24/0x40 net/netlink/genetlink.c:811
 netlink_unicast_kernel net/netlink/af_netlink.c:1304 [inline]
 netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1330
 netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1919
 sock_sendmsg_nosec net/socket.c:652 [inline]
 sock_sendmsg+0xcf/0x120 net/socket.c:672
 __sys_sendto+0x21c/0x320 net/socket.c:1975
 __do_sys_sendto net/socket.c:1987 [inline]
 __se_sys_sendto net/socket.c:1983 [inline]
 __x64_sys_sendto+0xdd/0x1b0 net/socket.c:1983
 do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x401b33
Code: ff ff ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb cd 66 0f 1f 44 00 00 83 3d dd 7b 2d 00 00 75 17 49 89 ca b8 2c 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 f1 0b 00 00 c3 48 83 ec 08 e8 57 01 00 00
RSP: 002b:00007ffd65808028 EFLAGS: 00000246 ORIG_RAX: 000000000000002c
RAX: ffffffffffffffda RBX: 00007ffd658080e0 RCX: 0000000000401b33
RDX: 0000000000000024 RSI: 00007ffd65808130 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007ffd65808030 R09: 000000000000000c
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007ffd65808130 R15: 0000000000000003


---
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.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

                 reply	other threads:[~2021-01-28 14:30 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=00000000000074fd2305b9f6b6be@google.com \
    --to=syzbot+e6d0c38bbcbe4d450b6c@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ramonreisfontes@gmail.com \
    --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.