IRC channel logs

<damo22>cat /proc/6/stat

<damo22>6 ( P ) R 1 1 1 0 0 0 0 0 0 0 1848 1402 0 0 18 -2 24 0 0 409063424 13940 0 0 0 ...

<damo22>ls -la /proc/6/exe

<damo22>lrwxrwxrwx 0 4294967295 root 1 Jan 1 1970 /proc/6/exe -> -

<damo22>but rumpdisk seems to be pushed down to 7

<damo22>so somehow the process is registering itself under the wrong PID

<damo22>i have no idea how this is possibe

<damo22>exe has the wrong values, but stat has correct values, just missing rumpdisk

<damo22>lrwxrwxrwx 0 4294967295 root 8 Jan 1 1970 /proc/7/exe -> rumpdisk <--- should be ext2fs

<gnu_srs2>damo22: Did you see:

<gnu_srs2>(09:08:54 PM) gnu_srs: damo22: Seems like arbiter+ext2fs shows the problem already w/o rumpdisk:

<gnu_srs2>(09:08:54 PM) gnu_srs: lrwxrwxrwx 0 4294967295 root 13 Jan 1 1970 /proc/2/exe -> /hurd/startup

<gnu_srs2>(09:08:54 PM) gnu_srs: lrwxrwxrwx 0 4294967295 root 13 Jan 1 1970 /proc/5/exe -> /hurd/startup

<gnu_srs2>(09:08:54 PM) gnu_srs: and no no fs process, as for normal boot: lrwxrwxrwx 0 4294967295 root 2 Jan 1 1970 5/exe -> fs

<damo22>ive been fiddling with the code so mine looks different

<damo22>it appears that PID 6 (rumpdisk) is being skipped in fsys_init() within libmachdev

<damo22>but the exe gets set on PID 7 -> rumpdisk

<damo22>which is actually ext2fs

<damo22>is it something to do with the fsys_init being the caller of fsys_init

<damo22>so somehow there could be an off by one on proc

<damo22>well its correct in libmachdev:

<damo22>EXE pci-arbiter(5)

<damo22>EXE rumpdisk(6)

<damo22>i printed the exe value and the pid

<damo22>so something is probably wrong with startup

2021-07-09.log