From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, Daniel Bond <danielbondno@gmail.com>
Cc: iwd@lists.linux.dev
Subject: Re: [PATCH 1/2] scan: fix invalid read when canceling an ongoing scan
Date: Thu, 5 Sep 2024 04:55:18 -0700 [thread overview]
Message-ID: <8eb5e60f-19ec-4ec7-8175-600f077d5a2d@gmail.com> (raw)
In-Reply-To: <7b6f85d6-136f-4b4e-9b67-f71879191cd1@gmail.com>
Hi Denis,
On 9/4/24 8:23 PM, Denis Kenzior wrote:
> Hi James,
>
>>>
>>> The issue seems to be resolved by checking that results->sr is set:
>>>
>>> - if (!results->sr->canceled)
>>> + if (results->sr && !results->sr->canceled)
>> The patch on the arch issue report looks good to me. Can we go ahead
>> and just send that patch with git send-email?
>
> Why is results->sr NULL?
>
> Is it caused by the cancellation path introduced by:
> 64d68b4f080c ("scan: fix invalid read when canceling an ongoing scan")
> ?
>
> Or is this caused by calling scan_get_results with a NULL sr like in
> scan_notify()? If sr is NULL, perhaps we shouldn't be invoking the
> survey path in the first place?
I'm looking more into this. Its related to an external scan which I can
now reproduce if I just remove my network profile and let IWD periodic
scan then issue an external one. Worse though is I see more invalid
reads related to the survey code path (when periodic scanning) so there
is more to it than I originally thought.
>
> Regards,
> -Denis
next prev parent reply other threads:[~2024-09-05 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 6:34 [PATCH 1/2] scan: fix invalid read when canceling an ongoing scan Daniel Bond
2024-09-03 11:44 ` James Prestwood
2024-09-03 17:03 ` Daniel Bond
2024-09-03 18:04 ` James Prestwood
2024-09-03 19:27 ` [PATCH] scan: add guard to check that results->sr is set to avoid segfault issue Daniel Bond
2024-09-05 3:23 ` [PATCH 1/2] scan: fix invalid read when canceling an ongoing scan Denis Kenzior
2024-09-05 11:55 ` James Prestwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 12:14 James Prestwood
2024-07-24 14:14 ` 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=8eb5e60f-19ec-4ec7-8175-600f077d5a2d@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