| 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
| ||
|
Date: Mon, 1 Dec 2014 07:54:30 +1100 From: Dave Chinner <david@...morbit.com> To: Richard Weinberger <richard@....at> Cc: x86@...nel.org, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, gregkh@...uxfoundation.org, rafael.j.wysocki@...el.com, pebolle@...cali.nl, linux-kernel@...r.kernel.org Subject: Re: [PATCH] x86: defconfig: Enable CONFIG_FHANDLE On Wed, Nov 26, 2014 at 12:36:52AM +0100, Richard Weinberger wrote: > systemd has a hard dependency on CONFIG_FHANDLE. > If you run systemd with CONFIG_FHANDLE=n it will somehow > boot but fail to spawn a getty or other basic services. > As systemd is now used by most x86 distributions it > makes sense to enabled this by default and save kernel > hackers a lot of value debugging time. The bigger question to me is this: why does systemd need to store/open by handle rather than just opening paths directly when needed? This interface is intended for stable, pathless access to inodes across unmount/mount contexts (e.g. userspace NFS servers, filesystem backup programs, etc) so I'm curious as to the problem systemd is solving using this interface. I just can't see the problem being solved here, and why path based security checks on every open() aren't necessary... Cheers, Dave. -- Dave Chinner david@...morbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists