FS#48328 - [linux-grsec] systemd boot freeze on archiso livecd with grsec and samba
Attached to Project:
Community Packages
Opened by Plague (centuryplague) - Thursday, 25 February 2016, 01:40 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 07 May 2016, 21:11 GMT
Opened by Plague (centuryplague) - Thursday, 25 February 2016, 01:40 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 07 May 2016, 21:11 GMT
|
Details
Description:
On a custom archiso build with linux-grsec kernel (with paxd) and stock samba package installed, presence of samba causes systemd pid 1 to freeze on bootup at the line "Reached target System Initialization." After a period of time, grsec reports that systemd pid 1 is frozen and keeps on waiting forever. Screenshot attached. The problem started occurring sometime in February 2016, I cannot give specific date because the livecd is built intermittently and another archiso syslinux bug was blocking. Only occurs with grsec kernel. The livecd is derived from archiso releng profile as described on Wiki. Package samba is included but the service is DISABLED on boot and contains no configuration. Prior to Febrary, there was no issue. If I remove samba from the livecd packages, the ISO boots successfully. Adding 'debug' to boot line gives no better information and I do not know how to debug this better on a live system. I have no non-live systems I can currently risk to test if this is an issue on non-live systems (with linux-grsec, paxd and samba). In the past, I once had a hang near this boot line that was caused by missing paxd exceptions. That is my only guess. Steps to reproduce: Build a livecd derived from archiso releng profile that uses linux-grsec, paxd, pax-utils, and samba packages, and that uses linux-grsec instead of linux (requires change to build.sh). Boot the ISO in a virtual machine or on USB stick. |
This task depends upon
Comment by
Daniel Micay (thestinger) -
Saturday, 05 March 2016, 12:28 GMT
Comment by Plague (centuryplague) -
Sunday, 06 March 2016, 02:38 GMT
Comment by
Daniel Micay (thestinger) -
Thursday, 21 April 2016, 12:08 GMT
Comment by Plague (centuryplague) -
Saturday, 07 May 2016, 17:43 GMT
Missing exceptions are an inherent limitation of the integration.
There will always be more. I'll happily add another exception but
you need to figure it out so I can then confirm it and add it.
You're going to need to do more debugging if you want this to be
solved.
Thanks for the reply. Frankly I couldn't understand how a disabled
service would cause this. It's low priority for myself (samba need
low, decided to scrap) and worse issues keep happening.
Any idea if this is still an issue?
Problem appears to have fixed itself. Somewhere between kernel 4.5
and samba updates it stopped being an issue and arch loads and
samba works fine.