public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Cc: Daniel Bond <danielbondno@gmail.com>
Subject: Re: [PATCH 1/2] scan: check scan request in get_survey_done before deref
Date: Thu, 5 Sep 2024 07:44:47 -0700	[thread overview]
Message-ID: <1fc65fe7-3e6f-4953-973c-84bde72bb2d1@gmail.com> (raw)
In-Reply-To: <fb4b3b86-e659-448b-bfb9-cfba35c2b87b@gmail.com>

Hi Denis,

On 9/5/24 7:37 AM, Denis Kenzior wrote:
> Hi James,
>
> On 9/5/24 8:43 AM, James Prestwood wrote:
>> Due to the possibility of external scans the scan request pointer
>
> Do we know why external scans are happening?  I can understand a one 
> off because someone triggered iw scan, but from the bug report it 
> sounded like it was crashing iwd repeatedly?
NetworkManager? wpa_supplicant running? I really have no idea. Either 
way its out of our control.
>
>> could be NULL. Prior to surveys IWD would still get the results in
>> order for periodic scans to utilize them. This behavior can be
>> retained by checking both if we don't have a request or if the
>> request was canceled. This check is identical to the one in
>> get_scan_done.
>>
>> This fixes a crash when checking if the NULL scan request has been
>> canceled:
>>
>> 0x00005ffa6a0376de in get_survey_done (user_data=0x5ffa783a3f90) at 
>> src/scan.c:2059
>> 0x0000749646a29bbd in ?? () from /usr/lib/libell.so.0
>> 0x0000749646a243cb in ?? () from /usr/lib/libell.so.0
>> 0x0000749646a24655 in l_main_iterate () from /usr/lib/libell.so.0
>> 0x0000749646a24ace in l_main_run () from /usr/lib/libell.so.0
>> 0x0000749646a263a4 in l_main_run_with_signal () from 
>> /usr/lib/libell.so.0
>> 0x00005ffa6a00d642 in main (argc=<optimized out>, argv=<optimized 
>> out>) at src/main.c:614
>>
>> Reported-by: Daniel Bond <danielbondno@gmail.com>
>> ---
>>   src/scan.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/src/scan.c b/src/scan.c
>> index debdeb1f..205365cd 100644
>> --- a/src/scan.c
>> +++ b/src/scan.c
>> @@ -2056,7 +2056,7 @@ static void get_survey_done(void *user_data)
>>         sc->get_survey_cmd_id = 0;
>>   -    if (!results->sr->canceled)
>> +    if (!results->sr || !results->sr->canceled)
>
> I still don't understand why we're even bothering requesting a survey 
> for a scan we didn't trigger?  In other words, we shouldn't even be in 
> this function.
Because we still utilize external scan results for periodic scans. So if 
periodic scans are running we will still try and get the survey/results.
>
>>           get_results(results);
>>       else
>>           get_scan_done(user_data);
>
> Regards,
> -Denis

  reply	other threads:[~2024-09-05 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 13:43 [PATCH 1/2] scan: check scan request in get_survey_done before deref James Prestwood
2024-09-05 13:43 ` [PATCH 2/2] scan: check pending requests after regdom update James Prestwood
2024-09-05 13:56 ` [PATCH 1/2] scan: check scan request in get_survey_done before deref James Prestwood
2024-09-05 14:37 ` Denis Kenzior
2024-09-05 14:44   ` James Prestwood [this message]
2024-09-05 14:57     ` Denis Kenzior
2024-09-05 15:09       ` James Prestwood

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=1fc65fe7-3e6f-4953-973c-84bde72bb2d1@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=danielbondno@gmail.com \
    --cc=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    /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