netdev - [powerpc] Fingerprint systemd service fails to start (next-20220624)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <B2AA3091-796D-475E-9A11-0021996E1C00@linux.ibm.com>
Date:   Mon, 27 Jun 2022 10:28:27 +0530
From:   Sachin Sant <sachinp@...ux.ibm.com>
To:     netdev@...r.kernel.org, kuniyu@...zon.com
Cc:     linuxppc-dev@...ts.ozlabs.org, davem@...emloft.net,
        linux-next@...r.kernel.org
Subject: [powerpc] Fingerprint systemd service fails to start (next-20220624)

With the latest -next I have observed a peculiar issue on IBM Power
server running -next(5.19.0-rc3-next-20220624) .

Fingerprint authentication systemd service (fprintd) fails to start while
attempting OS login after kernel boot. There is a visible delay of 18-20
seconds before being prompted for OS login password.

Kernel 5.19.0-rc3-next-20220624 on an ppc64le

ltcden8-lp6 login: root
<<=======.  delay of 18-20 seconds
Password: 

Following messages(fprintd service) are seen in /var/log/messages:

systemd[1]: Startup finished in 1.842s (kernel) + 1.466s (initrd) + 29.230s (userspace) = 32.540s.
NetworkManager[1100]: <info>  [1656304146.6686] manager: startup complete
dbus-daemon[1027]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.21' (uid=0 pid=1502 comm="/bin/login -p --      ")
systemd[1]: Starting Fingerprint Authentication Daemon...
fprintd[2521]: (fprintd:2521): fprintd-WARNING **: 00:29:08.568: Failed to open connection to bus: Could not connect: Connection refused
systemd[1]: fprintd.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: fprintd.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Fingerprint Authentication Daemon.
dbus-daemon[1027]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms)

Mainline (5.19.0-rc3) or older -next does not have this problem.

Git bisect between mainline & -next points to the following patch:

# git bisect bad
cf2f225e2653734e66e91c09e1cbe004bfd3d4a7 is the first bad commit
commit cf2f225e2653734e66e91c09e1cbe004bfd3d4a7

Date:   Tue Jun 21 10:19:12 2022 -0700

    af_unix: Put a socket into a per-netns hash table.

I don’t know how the above identified patch is related to the failure,
but given that I can consistently recreate the issue assume the bisect
result can be trusted.

I have attached dmesg log for reference. Let me know if any additional
Information is required.

Thanks
- Sachin

Download attachment "dmesg-next-20220624.log" of type "application/octet-stream" (28174 bytes)