Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1312031
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) |
| Date | 2016-01-19 10:20 +0100 |
| Message-ID | <qSACd-5IF-7@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <qPRSV-7T9-5@gated-at.bofh.it> <qPS2C-7X2-9@gated-at.bofh.it> <qQV86-2CA-5@gated-at.bofh.it> <qSzPP-5c2-5@gated-at.bofh.it> <qSAsy-5F1-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
* Peter Zijlstra <peterz@infradead.org> wrote: > On Tue, Jan 19, 2016 at 09:20:22AM +0100, Ingo Molnar wrote: > > + # newer systemd silently relies on the presence of the epoll system call: > > + select EPOLL > > + select ANON_INODES > > + > > + # newer systemd silently hangs durig early init without these: > > + select PROC_SYSCTL > > + select SYSCTL > > + select POSIX_MQUEUE > > + select POSIX_MQUEUE_SYSCTL > > + > > + # systemd needs this syscall: > > + select FHANDLE > > + > > + # systemd needs devtmpfs: "systemd[1]: Failed to mount devtmpfs at /dev: No such device" > > + select DEVTMPFS > > + > > + # systemd needs tmpfs: "systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory" > > + select SHMEM > > + select TMPFS > > + > > + # systemd needs timerfd syscalls: "[ 8.198625] systemd[1]: Failed to create timerfd: Function not implemented^" > > + select TIMERFD > > + > > + # systemd needs signalfd support: "[ 45.536725] systemd[1]: Failed to allocate manager object: Function not implemented" > > + select SIGNALFD > > + > > + # systemd hangs during bootup without cgroup support: > > + select CGROUPS > > + > > + # systemd fails during bootup without this option, with a nonsensical message: "[DEPEND] Dependency failed for File System Check on /dev/sda1." > > + select FILE_LOCKING > > + > > + # systemd fails during bootup without this option: > > + select FSNOTIFY > > + select INOTIFY_USER > > > And yes, many of these options are members of the 'SystemD debuggability Hall Of > > Shame'... It cost me many, many days of painful config-bisection to figure the > > often obscure dependencies out, so we might as well upstream this information. > > > > Many braincells died to bring us this information! > > So why not group those under CONFIG_SYSTEMD_BLOWS? I still dont have a > machine with that turd on. I'd definitely (try to) list the reasons for each quirk in the Kconfig lines (as I did above), but I'd still keep a single generic option not tied to systemd in particular, for the following reasons: - I am using many systemd systems, so the quirks are naturally mostly systemd related. There might be more non-systemd quirks that I never triggered personally. They can be added once people trigger them. - Also, even that considered, not all of the options I listed are systemd quirks, as I still have a single (albeit simple) non-systemd test machine. - I'd like to have a single superset option that principally makes the kernel 'just work' for newbie testers - without them having to be even aware of whether their distro version uses systemd or something else. Thanks, Ingo
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Ingo Molnar <mingo@kernel.org> - 2016-01-19 09:30 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Markus Trippelsdorf <markus@trippelsdorf.de> - 2016-01-19 09:50 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Ingo Molnar <mingo@kernel.org> - 2016-01-19 10:00 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Borislav Petkov <bp@suse.de> - 2016-01-19 10:50 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Peter Zijlstra <peterz@infradead.org> - 2016-01-19 10:10 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Ingo Molnar <mingo@kernel.org> - 2016-01-19 10:20 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) Borislav Petkov <bp@suse.de> - 2016-01-19 10:50 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y Michal Marek <mmarek@suse.cz> - 2016-01-19 11:00 +0100
Re: [RFC] CONFIG_GENERIC_BOOTABLE_CONFIG=y Ingo Molnar <mingo@kernel.org> - 2016-01-19 11:40 +0100
Re: [RFC] CONFIG_GENERIC_BOOTABLE_CONFIG=y Linus Torvalds <torvalds@linux-foundation.org> - 2016-01-19 18:30 +0100
Re: [RFC] CONFIG_GENERIC_BOOTABLE_CONFIG=y "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2016-01-19 19:00 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y Måns Rullgård <mans@mansr.com> - 2016-01-19 13:30 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y Michal Marek <mmarek@suse.cz> - 2016-01-19 13:50 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y Måns Rullgård <mans@mansr.com> - 2016-01-19 14:00 +0100
Re: [RFC] CONFIG_FORCE_MINIMALLY_SANE_CONFIG=y (was: Re: [RFC PATCH] x86/kconfig: Sanity-check config file during oldconfig) "Kirill A. Shutemov" <kirill@shutemov.name> - 2016-01-21 23:10 +0100
csiph-web