Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, baijiaju1990@gmail.com
Subject: Re: [PATCH] wifi: cfg80211: reinit wiphy work entries on runaway drain
Date: Tue, 7 Jul 2026 09:03:55 -0700	[thread overview]
Message-ID: <bac3152c-deb7-594e-0c8c-247acba5b7f2@candelatech.com> (raw)
In-Reply-To: <CAFRLqsXHZ75ktX0gb3HbJHyPLHa_iFr=qA8Z-G0Lz1ZEfLQKjQ@mail.gmail.com>

On 7/7/26 08:47, Cen Zhang wrote:
> Hi Ben,
> 
> Thanks for your review and comments.
> 
>> Even this likely leaves the system in a bad state since requested work
>> items would be skipped.  Probably should also increase runaway_limit quite
>> a bit as well (that has worked OK for me), maybe remove it entirely.
> 
> Fair. Hitting the guard still means pending work gets skipped; this patch only
> avoids leaving those work entries with stale list links after the
> existing drop path.
> 
> I was hesitant to remove the guard in the same change, because the
> flush-all paths run under the wiphy mutex, and a work item that keeps
> requeueing itself could otherwise keep flush, suspend, or unregister
> stuck there. Raising the limit sounds less risky, but I would want a
> concrete reason for the new value rather than picking one arbitrarily..

Yeah, you have a good point.  I'm not sure of a proper solution.  I set my limit to 200
and was no longer able to reproduce warning splats.

Your patch may certainly be an improvement.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



  reply	other threads:[~2026-07-07 16:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 13:49 [PATCH] wifi: cfg80211: reinit wiphy work entries on runaway drain Cen Zhang
2026-07-07 14:38 ` Ben Greear
2026-07-07 15:47   ` Cen Zhang
2026-07-07 16:03     ` Ben Greear [this message]
2026-07-07 17:31 ` Johannes Berg
2026-07-08  3:04   ` Cen Zhang

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=bac3152c-deb7-594e-0c8c-247acba5b7f2@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=baijiaju1990@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zzzccc427@gmail.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