Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53341 - [linux-grsec] systemd-logind mounts/unmounts tmpfs endlessly on boot
Attached to Project:
Community Packages
Opened by Scott Burman (osteichthyes) - Thursday, 16 March 2017, 21:46 GMT
Last edited by Daniel Micay (thestinger) - Monday, 20 March 2017, 14:58 GMT
Opened by Scott Burman (osteichthyes) - Thursday, 16 March 2017, 21:46 GMT
Last edited by Daniel Micay (thestinger) - Monday, 20 March 2017, 14:58 GMT
|
DetailsDescription:
Systemd hangs on boot with certain grsecurity hardened kernels. The issue arose near the end of 2016, and has persisted sporadically. The issue comes during boot, systemd creates, mounts, and then chdirs into a tmpfs. Immediately thereafter, the function fails, and repeats. The result is that it just mounts and unmounts the tmpfs until the system hangs. I've been working on it with the grsecurity team, here: https://forums.grsecurity.net/viewtopic.php?f=3&t=4676 I've also got a picture of the issue here: https://drive.google.com/file/d/0B7y3E9VTFdy4SjRvZ05BZkcxQjg/view?usp=sharing The issue was resolved in the 5 and 12 March patchsets, but arose again in the 15 March patchset. It does not occur in the kernel built for the repos by nning. Interestingly, even using nning's configureation file can yield a kernel that causes this error. I know that this isn't the most informative bug report, but it happens during boot, before I can get to a terminal or anything, so my ability to get logs is limited. I think it's at least similar to this: https://bugzilla.redhat.com/show_bug.cgi?id=1075835 Additional info: * package version(s) Currently, the kernel is 4.9.15 systemd: 232-8 Again, this arose near the end of 2016, at which point the kernel was around 4.8.10 or so, I'm not sure where systemd was at. * config and/or log files etc. See the images and links above. Steps to reproduce: Build a recent version of the grsecurity kernel -- not every version causes this. The patchset from 15 March does, the patchset from 12 March does not. The issue started to pop-up intermittently around the 4.8.10 patchset. |
This task depends upon
Comment by Daniel Micay (thestinger) -
Saturday, 18 March 2017, 06:08 GMT
Does this occur with the official build of the package?
Comment by Scott Burman (osteichthyes) -
Sunday, 19 March 2017, 01:14 GMT
Typically, it does not. It does with the official build config, but not the precompiled binary. That's what is so confounding.
Comment by Scott Burman (osteichthyes) -
Monday, 20 March 2017, 06:30 GMT
I wonder if this isn't a build environment issue. I tried building with no grsecurity patches at some point in the 40+ different builds I tried. That failed, too.
Comment by Daniel Micay (thestinger) -
Monday, 20 March 2017, 14:57 GMT
Well then this doesn't sound like a bug in this package. You should use devtools to build in a container as we do for official packages, but it sounds like there's something wrong with your installation that you should probably look into.