On Tue, 2017-07-11 at 09:35 +0200, Lennart Poettering wrote: > Normally it's dead cheap to check that, it's just reading and > comparing one memory location. It's a pitty that this isn't the case > currently on Debian, but as it appears this is an oversight on their > side, and I am sure it will be eventually fixed there, if it hasn't > already.
Are you sure about those "Debian only" and "will be 'fixed'" parts? The Debian patch seems to be a cherry pick from upstream glibc. Is there evidence of some error that would cause effects only visible on Debian and nowhere else? And/or has the change been reverted or behavior otherwise modified upstream to limit the range of relevant versions? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
