init stuck on PD session from platform_drv

[Boris Mulder]

Hi all,

I have a scenario with many inits on top of each other, and somewhere
lives the wifi_drv. When I add another init called 'init_wifi' on top so
I can try to kill/restart the wifi_drv, the system hangs and I get the
following log:

[init -> init_system -> init_user -> init_wifi] child "wifi_drv"
[init -> init_system -> init_user -> init_wifi]   RAM quota:  130816K
[init -> init_system -> init_user -> init_wifi]   cap quota:  168
[init -> init_system -> init_user -> init_wifi]   ELF binary: wifi_drv
[init -> init_system -> init_user -> init_wifi]   priority:   0
[init -> init_system -> init_user -> init_wifi]   provides service Nic
[init -> init_system -> init_user -> init_wifi] child "nic_dump"
announces service "Nic"
Error: corrupted string
[init -> init_system -> init_user -> init_wifi -> wifi_drv] Reload
wpa_supplicant configuration
[init] Warning: re-attempted PD session request 2 times (args:
virt_space=0, phys_start=0x0, phys_size=0x100000000, diag=0,
label="platform_drv -> init_system -> init_user -> init_wifi -> wifi_drv
-> ", cap_quota=13)
[init] Warning: re-attempted PD session request 4 times (args:
virt_space=0, phys_start=0x0, phys_size=0x100000000, diag=0,
label="platform_drv -> init_system -> init_user -> init_wifi -> wifi_drv
-> ", cap_quota=13)
[init] Warning: re-attempted PD session request 8 times (args:
virt_space=0, phys_start=0x0, phys_size=0x100000000, diag=0,
label="platform_drv -> init_system -> init_user -> init_wifi -> wifi_drv
-> ", cap_quota=13)
[init] Warning: re-attempted PD session request 16 times (args:
virt_space=0, phys_start=0x0, phys_size=0x100000000, diag=0,
label="platform_drv -> init_system -> init_user -> init_wifi -> wifi_drv
-> ", cap_quota=13)
etcetera, with double retries each time.

Now when this happens the whole system hangs, nothing else is working
anymore.

As soon as the wifi_drv is started, this problem occurs.

When I did not have init_wifi and the wifi_drv was running on top of
init_user, everything worked fine. Of course, I adjusted all the routes
and policies (of the platform_drv) accordingly.

Could the label be too long for core to handle perhaps, or is something
else happening? What do these error messages mean and why do they pop up
now and not with one init less?

-- 

Met vriendelijke groet / kind regards,

Boris Mulder

Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands
+31 35 631 3253 (office)