From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Lukas Redlinger <rel+kernel@agilox.net>, linux-wireless@vger.kernel.org
Cc: j@w1.fi
Subject: Re: BUG: using smp_processor_id() in preemptible [00000000] code: wpa_supplicant
Date: Fri, 13 Sep 2019 14:11:05 +0200 [thread overview]
Message-ID: <87k1acs8fa.fsf@toke.dk> (raw)
In-Reply-To: <CAN5HydrWb3o_FE6A1XDnP1E+xS66d5kiEuhHfiGKkLNQokx13Q@mail.gmail.com>
Lukas Redlinger <rel+kernel@agilox.net> writes:
> Hello,
>
> on Arch Linux 5.2.11 with wpa_supplicant 2.8 / 2.9 our systems
> increasingly show this issue:
>
> [72770.969617] BUG: using smp_processor_id() in preemptible [00000000]
> code: wpa_supplicant/16207
> [72770.969638] caller is ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
> [72770.969640] CPU: 2 PID: 16207 Comm: wpa_supplicant Tainted: G
> W 5.2.11-arch1-1-ARCH #1
> [72770.969641] Hardware name: CINCOZE DI-1000/DI-1000, BIOS 5.11 02/20/2019
> [72770.969642] Call Trace:
> [72770.969647] dump_stack+0x5c/0x80
> [72770.969661] debug_smp_processor_id+0xde/0xe0
> [72770.969674] ieee80211_xmit_fast_finish+0x5a/0x1e0 [mac80211]
> [72770.969687] ieee80211_tx_dequeue+0x472/0xb50 [mac80211]
> [72770.969695] iwl_mvm_mac_itxq_xmit+0x6f/0x100 [iwlmvm]
> [72770.969721] _ieee80211_wake_txqs+0x218/0x450 [mac80211]
> [72770.969733] ieee80211_wake_queues_by_reason+0x7a/0xd0 [mac80211]
> [72770.969745] ieee80211_set_disassoc+0x48d/0x5d0 [mac80211]
> [72770.969760] ieee80211_mgd_deauth.cold+0x4a/0x3f4 [mac80211]
> [72770.969797] cfg80211_mlme_deauth+0xc1/0x220 [cfg80211]
> [72770.969809] nl80211_deauthenticate+0xd8/0x120 [cfg80211]
> [72770.969813] genl_family_rcv_msg+0x1f3/0x470
> [72770.969815] genl_rcv_msg+0x47/0x90
> [72770.969818] ? __kmalloc_node_track_caller+0x1b7/0x2d0
> [72770.969819] ? genl_family_rcv_msg+0x470/0x470
> [72770.969820] netlink_rcv_skb+0x75/0x140
> [72770.969822] genl_rcv+0x24/0x40
> [72770.969823] netlink_unicast+0x177/0x1f0
> [72770.969824] netlink_sendmsg+0x1fe/0x3c0
> [72770.969827] sock_sendmsg+0x4f/0x60
> [72770.969828] ___sys_sendmsg+0x304/0x370
> [72770.969831] ? unix_ioctl+0x99/0x190
> [72770.969834] __sys_sendmsg+0x81/0xd0
> [72770.969850] do_syscall_64+0x5f/0x1d0
> [72770.969851] ? prepare_exit_to_usermode+0x85/0xb0
> [72770.969853] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Hmm, ieee80211_set_disassoc() has a call to ieee80211_flush_queues();
but that only calls into the driver, it doesn't flush the TXQ. Maybe we
need to add that?
-Toke
prev parent reply other threads:[~2019-09-13 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 5:51 BUG: using smp_processor_id() in preemptible [00000000] code: wpa_supplicant Lukas Redlinger
2019-09-13 12:11 ` Toke Høiland-Jørgensen [this message]
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=87k1acs8fa.fsf@toke.dk \
--to=toke@redhat.com \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=rel+kernel@agilox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).