linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Arnesen <harald@skogtun.org>
To: Johannes Berg <johannes@sipsolutions.net>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BISECTED] 5.12 hangs at reboot
Date: Mon, 26 Apr 2021 22:25:36 +0200	[thread overview]
Message-ID: <f02ad718-654e-6e60-f199-4512b1afd1f4@skogtun.org> (raw)
In-Reply-To: <bca302812cece1972bed7efe34a9d554b9e912ed.camel@sipsolutions.net>

Johannes Berg [26.04.2021 22:11]:

> Oh, I have another idea - maybe void linux is using iwd instead of
> wpa_supplicant, and that insists on doing the netlink owner stuff so
> everything is deleted in case it crashes. But I've been looking at the
> code pretty much assuming that we get actual calls down, so ...

It is indeed using iwd:

$ ps ax | grep wpa
$
$ ps ax | grep iwd
  996 ?        Ss     0:00 runsv iwd
 1395 ?        S      0:00 /usr/libexec/iwd
$
-- 
Hilsen Harald

  reply	other threads:[~2021-04-26 20:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 18:43 [BISECTED] 5.12 hangs at reboot Harald Arnesen
2021-04-26 18:59 ` Linus Torvalds
2021-04-26 19:19   ` Johannes Berg
2021-04-26 20:23     ` Harald Arnesen
2021-04-26 19:29   ` Harald Arnesen
2021-04-26 19:38     ` Johannes Berg
2021-04-26 19:45       ` Linus Torvalds
2021-04-26 19:46         ` Johannes Berg
2021-04-26 19:51           ` Linus Torvalds
2021-04-26 20:11             ` Johannes Berg
2021-04-26 20:25               ` Harald Arnesen [this message]
     [not found]       ` <151b7e41-a415-e780-eb90-6ca16c113066@skogtun.org>
2021-04-26 22:49         ` Linus Torvalds
2021-04-27  7:43           ` Herbert Xu
2021-04-27  8:49           ` Johannes Berg
2021-04-26 20:10   ` Harald Arnesen
2021-04-26 20:26     ` Johannes Berg

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=f02ad718-654e-6e60-f199-4512b1afd1f4@skogtun.org \
    --to=harald@skogtun.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).