Description of problem: Autofs 5.1.5-2 and up immediately coredumps on any line in /etc/auto.master containing a multi-map Version-Release number of selected component (if applicable): autofs-5.1.5-3.fc30.x86_64 Broken (=current) autofs-5.1.5-2.fc30.x86_64 Broken autofs-5.1.5-1.fc30.x86_64 Okay (= last version with hesiod compiled in) autofs-5.1.4-21.fc29.x86_64 Okay How reproducible: Always and immediate. Steps to Reproduce: 1. Comment out everything in /etc/auto.master and add one line: /test multi /etc/auto.test -- /etc/auto.test1 2. Make /etc/auto.test contain one line: one -fstype=bind :/usr/data Make /etc/auto.test1 contain one line: two -fstype=bind :/usr/data/tmp 3. systemctl restart autofs Actual results: ---- [root@funen tmp]# systemctl start autofs Job for autofs.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status autofs.service" and "journalctl -xe" for details. ---- In the journal, there is: ---- -- -- The unit UNIT has successfully entered the 'dead' state. May 14 09:13:08 funen.esat.kuleuven.be systemd[1]: autofs.service: Main process exited, code=dumped, status=11/SEGV -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ---- Expected results: Successful start, and correct behaviour when for 'ls -l /test/one' resp. 'ls -l /test/two' Additional info: *) Nothing is logged *) Just the word 'multi' alone is enough to cause a crash. *) As the difference between the last-good and first-bad (according to what is in Koji) is only ---- * Mon Nov 05 2018 Ian Kent <ikent> - 1:5.1.5-2 - update spec file to build without hesiod. ---- it should be related to the removal of hesiod. Not that there's no hesiod used here at all. Greetings, Bert.
Oh dear, very sorry about this. I am aware of this problem and thought I had fixed it in Fedora. I'll get an update out as soon as I can.
autofs-5.1.5-4.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ca7e629af8
Could you check this change resolves the problem when it arrives in the testing repo please. Also please add feedback about the test result at the link above.
Hi Ian, autofs-5.1.5-4.fc30.x86_64 from Koji indeed fixes the problem. You should get a medal for one of the fastest bugfixes in Fedora's history! Thanks! B.
autofs-5.1.5-4.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ca7e629af8
autofs-5.1.5-4.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.