Bug#787000: Failed to set memory.limit_in_bytes on : Invalid argument

[Moyer, Keith]

Package: systemd
Version: 215-12
Severity: minor
Tags: upstream patch fixed-upstream

When I have a "MemoryLimit" set on a single service unit, I get a "systemd[1]: Failed to set memory.limit_in_bytes on : Invalid argument" error message during boot.  Removing the "MemoryLimit" makes the error message go away.

>From the error message, it can be seen that this attribute is being set on the root cgroup (due to no text between "on" and ":"), which is indeed invalid.  This has been fixed upstream in v219 with the following two trivial commits (the first commit has a typo that the second corrects):
http://cgit.freedesktop.org/systemd/systemd/commit/src/core/cgroup.c?id=75399049653f2d5e22032da70cf96f20d7b4d9a6
http://cgit.freedesktop.org/systemd/systemd/commit/src/core/cgroup.c?id=a3bd89ea99214db7ca2ad6ae59181d5119a54f09

This doesn't appear to be fixed in either the jessie or master branches in the Debian repository:
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/src/core/cgroup.c?h=6353e34a2056eb6e9e4040aa01f139bfb8904603#n370
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/src/core/cgroup.c?h=b1e8aa81062a0fcbcc27b99144521579ab873245#n370

As far as I can tell, the risk is miniscule; all it does is skip trying to set this attribute when the path is the root cgroup (which is an invalid thing to try and would error out anyway).

Can this simple fix be pulled in, preferably into jessie?