Bug 98321 - mac80211 crash: Failed check-sdata-in-driver check
Summary: mac80211 crash: Failed check-sdata-in-driver check
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 high
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-14 02:44 UTC by nanericwang
Modified: 2020-08-20 15:50 UTC (History)
8 users (show)

See Also:
Kernel Version: 4.0.3
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description nanericwang 2015-05-14 02:44:10 UTC
May 14 08:15:14 archnet kernel: ------------[ cut here ]------------
May 14 08:15:14 archnet kernel: WARNING: CPU: 0 PID: 204 at net/mac80211/driver-ops.h:12 ieee80211_set_tx_power+0x46/0x1a0 [mac80211]()
May 14 08:15:14 archnet kernel: wlp1s0:  Failed check-sdata-in-driver check, flags: 0x0
May 14 08:15:14 archnet kernel: Modules linked in: arc4 ath9k led_class ath9k_common ath9k_hw mac80211 ath acpi_cpufreq crct10dif_pclmul crct10dif_common crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw cfg80211 gf128mu
May 14 08:15:14 archnet kernel: CPU: 0 PID: 204 Comm: iw Tainted: G           O    4.0.3-1-ck #1
May 14 08:15:14 archnet kernel: Hardware name: BIOSTAR Group A68N-5000/A68N-5000, BIOS 4.6.5 04/22/2014
May 14 08:15:14 archnet kernel:  0000000000000000 ffffffffa0338874 ffffffff812f73cf ffff8800e8a17a28
May 14 08:15:14 archnet kernel:  ffffffff81042707 0000000000000001 ffff8800e7cea000 ffff8800e7cea850
May 14 08:15:14 archnet kernel:  ffff8800e8a28260 0000000000000000 ffffffff81042785 ffffffffa0336788
May 14 08:15:14 archnet kernel: Call Trace:
May 14 08:15:14 archnet kernel:  [<ffffffff812f73cf>] ? dump_stack+0x40/0x50
May 14 08:15:14 archnet kernel:  [<ffffffff81042707>] ? warn_slowpath_common+0x77/0xb0
May 14 08:15:14 archnet kernel:  [<ffffffff81042785>] ? warn_slowpath_fmt+0x45/0x50
May 14 08:15:14 archnet kernel:  [<ffffffff811a1ae8>] ? rhashtable_lookup_compare+0x58/0x90
May 14 08:15:14 archnet kernel:  [<ffffffffa030fe96>] ? ieee80211_set_tx_power+0x46/0x1a0 [mac80211]
May 14 08:15:14 archnet kernel:  [<ffffffffa025dea0>] ? nl80211_set_wiphy+0x2d0/0x5c0 [cfg80211]
May 14 08:15:14 archnet kernel:  [<ffffffff8128b2bd>] ? netlink_sendskb+0xd/0x40
May 14 08:15:14 archnet kernel:  [<ffffffff81196388>] ? number.isra.2+0x2c8/0x2f0
May 14 08:15:14 archnet kernel:  [<ffffffff811ab41a>] ? nla_parse+0xaa/0x108
May 14 08:15:14 archnet kernel:  [<ffffffff8128c986>] ? genl_family_rcv_msg+0x1c6/0x348
May 14 08:15:14 archnet kernel:  [<ffffffff8128cb08>] ? genl_family_rcv_msg+0x348/0x348
May 14 08:15:14 archnet kernel:  [<ffffffff8128cb64>] ? genl_rcv_msg+0x5c/0xb8
May 14 08:15:14 archnet kernel:  [<ffffffff8128bcb8>] ? netlink_rcv_skb+0x98/0xb8
May 14 08:15:14 archnet kernel:  [<ffffffff8128c7af>] ? genl_rcv+0x1f/0x30
May 14 08:15:14 archnet kernel:  [<ffffffff8128b3f4>] ? netlink_unicast+0x104/0x180
May 14 08:15:14 archnet kernel:  [<ffffffff8128ba17>] ? netlink_sendmsg+0x4e7/0x5e0
May 14 08:15:14 archnet kernel:  [<ffffffff810fdc72>] ? d_instantiate+0x32/0x50
May 14 08:15:14 archnet kernel:  [<ffffffff8113e04a>] ? proc_lookup_de+0x9a/0xa8
May 14 08:15:14 archnet kernel:  [<ffffffff8124b3e6>] ? do_sock_sendmsg+0x3e/0x68
May 14 08:15:14 archnet kernel:  [<ffffffff8124c698>] ? ___sys_sendmsg+0x2b8/0x2c0
May 14 08:15:14 archnet kernel:  [<ffffffff810c6e12>] ? do_set_pte+0x72/0xa8
May 14 08:15:14 archnet kernel:  [<ffffffff81253bf8>] ? skb_queue_purge+0x18/0x20
May 14 08:15:14 archnet kernel:  [<ffffffff810c8a2d>] ? handle_mm_fault+0x58d/0x12f0
May 14 08:15:14 archnet kernel:  [<ffffffff8111f4b7>] ? fsnotify_clear_marks_by_inode+0x97/0xa0
May 14 08:15:14 archnet kernel:  [<ffffffff8124d453>] ? __sys_sendmsg+0x3b/0x70
May 14 08:15:14 archnet kernel:  [<ffffffff812fb832>] ? system_call_fastpath+0x12/0x17
May 14 08:15:14 archnet kernel: ---[ end trace 291d7c1204929c14 ]---
Comment 1 Johannes Berg 2015-05-14 19:10:13 UTC
Yeah, I've seen this before, the interface is down when this happens I believe.

No idea what caused it though, but should be easy to fix, any takers? :)
Comment 2 smurfendrek123 2020-07-24 19:37:34 UTC
I just had this bug on 5.7.7-200.fc32.x86_64 and made a bug report on the fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1851185

There's also a related report on ubuntu's launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882419
Comment 3 Dan Egnor 2020-08-20 15:50:47 UTC
This (or something very similar) happened to me as well:

Aug 19 04:59:23 skully kernel: [67510.402179] ------------[ cut here ]------------
Aug 19 04:59:23 skully kernel: [67510.402182] wlp3s0:  Failed check-sdata-in-driver check, flags: 0x0
Aug 19 04:59:23 skully kernel: [67510.402208] WARNING: CPU: 2 PID: 11396 at net/mac80211/driver-ops.h:17 drv_sta_state+0x254/0x3f0 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402210] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio binfmt_misc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm mei_hdcp crct10dif_pclmul ghash_clmulni_intel snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_usb_audio snd_usbmidi_lib snd_hwdep aesni_intel snd_seq_midi iwlmvm crypto_simd snd_seq_midi_event cryptd glue_helper intel_cstate mac80211 uvcvideo videobuf2_vmalloc intel_rapl_perf videobuf2_memops libarc4 snd_rawmidi videobuf2_v4l2 videobuf2_common iwlwifi snd_pcm snd_seq videodev btusb snd_seq_device i915 mc joydev input_leds btrtl snd_timer btbcm intel_wmi_thunderbolt btintel snd bluetooth cfg80211 mei_me drm_kms_helper soundcore mei i2c_algo_bit intel_pch_thermal ecdh_generic fb_sys_fops ecc syscopyarea sysfillrect sysimgblt ir_rc6_decoder rc_rc6_mce nuvoton_cir rc_core acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp
Aug 19 04:59:23 skully kernel: [67510.402254]  parport drm ip_tables x_tables autofs4 hid_generic usbhid hid crc32_pclmul e1000e sdhci_pci ahci cqhci i2c_i801 sdhci libahci wmi video
Aug 19 04:59:23 skully kernel: [67510.402257] CPU: 2 PID: 11396 Comm: kworker/u16:2 Tainted: G        W         5.4.0-42-generic #46-Ubuntu
Aug 19 04:59:23 skully kernel: [67510.402258] Hardware name:  /NUC6i7KYB, BIOS KYSKLi70.86A.0059.2018.1122.1431 11/22/2018
Aug 19 04:59:23 skully kernel: [67510.402272] Workqueue: phy0 ieee80211_csa_connection_drop_work [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402286] RIP: 0010:drv_sta_state+0x254/0x3f0 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402288] Code: 00 45 31 ed e9 66 fe ff ff 48 8b 83 78 04 00 00 48 8d b3 98 04 00 00 48 c7 c7 c8 68 a1 c0 48 85 c0 48 0f 45 f0 e8 57 c1 10 f6 <0f> 0b 41 bd fb ff ff ff e9 3d fe ff ff 65 8b 05 e8 ac 67 3f 89 c0
Aug 19 04:59:23 skully kernel: [67510.402288] RSP: 0018:ffffad69c7a9bc98 EFLAGS: 00010282
Aug 19 04:59:23 skully kernel: [67510.402289] RAX: 0000000000000000 RBX: ffff8da4176488c0 RCX: 0000000000000006
Aug 19 04:59:23 skully kernel: [67510.402290] RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff8da41ea978c0
Aug 19 04:59:23 skully kernel: [67510.402291] RBP: ffffad69c7a9bcd0 R08: 00000000509a06a0 R09: 0000000000000004
Aug 19 04:59:23 skully kernel: [67510.402291] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8da4176b07a0
Aug 19 04:59:23 skully kernel: [67510.402291] R13: ffff8da4176b07a0 R14: 0000000000000004 R15: ffff8da4176b0d68
Aug 19 04:59:23 skully kernel: [67510.402292] FS:  0000000000000000(0000) GS:ffff8da41ea80000(0000) knlGS:0000000000000000
Aug 19 04:59:23 skully kernel: [67510.402293] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 19 04:59:23 skully kernel: [67510.402293] CR2: 00007f81f39aa028 CR3: 000000033560a005 CR4: 00000000003606e0
Aug 19 04:59:23 skully kernel: [67510.402294] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 19 04:59:23 skully kernel: [67510.402294] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Aug 19 04:59:23 skully kernel: [67510.402295] Call Trace:
Aug 19 04:59:23 skully kernel: [67510.402304]  sta_info_move_state+0x276/0x370 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402319]  __sta_info_destroy_part2+0x2f/0x180 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402334]  __sta_info_flush+0x128/0x180 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402349]  ieee80211_set_disassoc+0xc0/0x5f0 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402354]  ? _raw_spin_unlock_bh+0x1e/0x20
Aug 19 04:59:23 skully kernel: [67510.402369]  __ieee80211_disconnect+0x86/0x120 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402380]  ieee80211_csa_connection_drop_work+0x15/0x20 [mac80211]
Aug 19 04:59:23 skully kernel: [67510.402383]  process_one_work+0x1eb/0x3b0
Aug 19 04:59:23 skully kernel: [67510.402387]  worker_thread+0x4d/0x400
Aug 19 04:59:23 skully kernel: [67510.402391]  kthread+0x104/0x140
Aug 19 04:59:23 skully kernel: [67510.402394]  ? process_one_work+0x3b0/0x3b0
Aug 19 04:59:23 skully kernel: [67510.402397]  ? kthread_park+0x90/0x90
Aug 19 04:59:23 skully kernel: [67510.402400]  ret_from_fork+0x35/0x40
Aug 19 04:59:23 skully kernel: [67510.402403] ---[ end trace f0619759527e8d71 ]---

Linux skully 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Seems to happen every few days, happy to instrument & collect more data or whatever.

Note You need to log in before you can comment on or make changes to this bug.