From: Johannes Berg <johannes@sipsolutions.net>
To: Vladislav Efanov <VEfanov@ispras.ru>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] cfg80211: Convert WARN_ON() to warning message
Date: Thu, 26 Sep 2024 21:51:45 +0200 [thread overview]
Message-ID: <84336e03a2634f0d1305cfbdfbae516a7a67364a.camel@sipsolutions.net> (raw)
In-Reply-To: <20240926133446.25445-1-VEfanov@ispras.ru>
On Thu, 2024-09-26 at 16:34 +0300, Vladislav Efanov wrote:
> syzkaller got the following warning:
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 9992 at net/wireless/ibss.c:36 __cfg80211_ibss
>
> This warning is the result of the race condition between the following
> events:
>
> event1 event2 event3
> __ieee80211_sta_join_ibss() | |
> creates new cgf80211_bss | |
> structure. | |
> Calls cfg80211_ibss_joined() | |
> which will scheduled | |
> new event_work. | |
> ieee80211_ibss_disconnect() |
> is called due to connection |
> dropped/ibss leaves to |
> remove cfg80211_bss structure. |
> event_work starts.
> __cfg80211_ibss_joined()
>
Seems almost better though to solve it by removing the pending work when
disconnecting?
johannes
prev parent reply other threads:[~2024-09-26 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 13:34 Vladislav Efanov
2024-09-26 15:58 ` Kalle Valo
2024-09-26 19:51 ` Johannes Berg [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=84336e03a2634f0d1305cfbdfbae516a7a67364a.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=VEfanov@ispras.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®