From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH] station: check for roam timeout before rearming
Date: Tue, 3 Sep 2024 10:18:31 -0500 [thread overview]
Message-ID: <538945e8-2ecd-4d65-94b9-a2839d5052cc@gmail.com> (raw)
In-Reply-To: <20240829112758.35494-1-prestwoj@gmail.com>
Hi James,
On 8/29/24 6:27 AM, James Prestwood wrote:
> A user reported a crash which was due to the roam trigger timeout
> being overwritten, followed by a disconnect. Post-disconnect the
> timer would fire and result in a crash. Its not clear exactly where
> the overwrite was happening but upon code inspection it could
> happen in the following scenario:
>
> 1. Beacon loss event, start roam timeout
> 2. Signal low event, no check if timeout is running and the timeout
> gets overwritten.
>
> The reported crash actually didn't appear to be from the above
> scenario but something else, so this logic is being hardened and
> improved
>
> Now if a roam timeout already exists and trying to be rearmed IWD
> will check the time remaining on the current timer and either keep
> the active timer or reschedule it to the lesser of the two values
> (current or new rearm time). This will avoid cases such as a long
> roam timer being active (e.g. 60 seconds) followed by a beacon or
> packet loss event which should trigger a more agressive roam
> schedule.
> ---
> src/station.c | 48 +++++++++++++++++++++++++++++-------------------
> 1 file changed, 29 insertions(+), 19 deletions(-)
>
Applied, thanks.
Regards,
-Denis
next prev parent reply other threads:[~2024-09-03 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 11:27 [PATCH] station: check for roam timeout before rearming James Prestwood
2024-09-03 15:18 ` Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-27 14:10 James Prestwood
2024-08-28 2:36 ` Denis Kenzior
2024-08-28 12:08 ` James Prestwood
2024-08-28 14:41 ` Denis Kenzior
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=538945e8-2ecd-4d65-94b9-a2839d5052cc@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@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