Wireless Daemon for Linux
 help / color / mirror / Atom feed
To: iwd at lists.01.org
Subject: Re: iwd 1.23 crashes in eapol_handle_pkt_1_of_4()
Date: Thu, 03 Feb 2022 12:35:21 +0100	[thread overview]
Message-ID: <871r0kchdy.fsf@toke.dk> (raw)
In-Reply-To: 87a6f9c4f5.fsf@toke.dk

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

Toke Høiland-Jørgensen <toke(a)toke.dk> writes:

> Denis Kenzior <denkenz(a)gmail.com> writes:
>
>> Hi Toke,
>>
>> On 2/2/22 06:05, Toke Høiland-Jørgensen wrote:
>>> Hi
>>> 
>>> Since updating to iwd 1.23 (from Arch packages), I've started seeing
>>> periodic crashes. I rebuilt iwd with debug symbols enabled and got the
>>> following backtrace out of 'coredumpctl gdb':
>>> 
>>
>> *hangs his head in shame*.  So I think we screwed up the same macro 2x now.
>
> Heh, yeah, did see there was a commit touching that macro, but didn't
> look closer.
>
>> Can you please try the patch I just sent out?
>
> Can do - thanks! Did a build with it incorporated and am running that
> now. Usually crashes once every hour (with striking regularity); will
> leave it running overnight and see if the crashes are gone by tomorrow
> :)

Alright, so no crashes - thanks for the swift fix!

And just for future reference, in case anyone else runs into the same
issue: The crashes were initially taking the kernel down with them,
which has now also been fixed:
https://lore.kernel.org/r/20220201130951.22093-1-johannes(a)sipsolutions.net

-Toke

             reply	other threads:[~2022-02-03 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 11:35  [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-02 22:03 iwd 1.23 crashes in eapol_handle_pkt_1_of_4() 
2022-02-02 17:16 Denis Kenzior
2022-02-02 15:05 
2022-02-02 13:04 Diederik de Haas
2022-02-02 12:05 

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=871r0kchdy.fsf@toke.dk \
    --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