Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH] station: Add missing netconfig_reset()
Date: Wed, 29 Sep 2021 18:12:03 -0500	[thread overview]
Message-ID: <082cbccd-46d4-7f99-16cf-e57a5702881c@gmail.com> (raw)
In-Reply-To: 20210929222201.124492-1-andrew.zaborowski@intel.com

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

Hi Andrew,

On 9/29/21 5:22 PM, Andrew Zaborowski wrote:
> On NETDEV_EVENT_DISCONNECT_BY_* events during netconfig, we'd forget to
> call netconfig_reset() before trying a new netconfig_configure()
> resulting in the "netconfig: Failed to start DHCPv4 client for interface
> %u" warning and a L_WARN_ON.  Add the missing call.

So you're still not including the useful information that would be very useful 
that was mentioned in the earlier thread...

> ---
>   src/station.c | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/src/station.c b/src/station.c
> index 934815f2..1c073fc1 100644
> --- a/src/station.c
> +++ b/src/station.c
> @@ -2810,6 +2810,9 @@ static void station_disconnect_event(struct station *station, void *event_data)
>   	switch (station->state) {
>   	case STATION_STATE_CONNECTING:
>   	case STATION_STATE_CONNECTING_AUTO:
> +		if (station->netconfig)
> +			netconfig_reset(station->netconfig);
> +

NAK.  This is still not addressing the underlying bug.  It should not go via the 
station_connect_cb path at all.  Perhaps you need to add a new 
CONNECTED_NETCONFIG state instead.

>   		station_connect_cb(station->netdev,
>   					NETDEV_RESULT_HANDSHAKE_FAILED,
>   					event_data, station);
> 

Regards,
-Denis

             reply	other threads:[~2021-09-29 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 23:12 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-29 22:22 [PATCH] station: Add missing netconfig_reset() Andrew Zaborowski

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=082cbccd-46d4-7f99-16cf-e57a5702881c@gmail.com \
    --to=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