<div dir="ltr">Yes, this is one of the things I fixed in an upcoming patch set I should send out very soon. In the patch that addresses this issue, I have a slightly more robust solution during dump and it also checks during restore for the case of missing properties in the event of migration between different kernel versions with different cgroup properties.<br>
<div><br></div><div>Thank you for looking into this Tycho. Give me a little time and I will send out my solution.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 12, 2014 at 12:31 PM, Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We shouldn't require specific properties to be enabled when dumping, we should<br>
just dump them if they happen to be set.<br>
<br>
Cc: Garrison Bellack <<a href="mailto:gbellack@google.com">gbellack@google.com</a>><br>
Signed-off-by: Tycho Andersen <<a href="mailto:tycho.andersen@canonical.com">tycho.andersen@canonical.com</a>><br>
---<br>
cgroup.c | 4 ++++<br>
1 file changed, 4 insertions(+)<br>
<br>
diff --git a/cgroup.c b/cgroup.c<br>
index 8308413..f98b40f 100644<br>
--- a/cgroup.c<br>
+++ b/cgroup.c<br>
@@ -409,6 +409,10 @@ static int add_cgroup_properties(const char *fpath, struct cgroup_dir *ncd,<br>
}<br>
if (read_cgroup_prop(prop, fpath) < 0) {<br>
free_cgroup_prop(prop);<br>
+<br>
+ if (errno == ENOENT)<br>
+ continue;<br>
+<br>
free_all_cgroup_props(ncd);<br>
return -1;<br>
}<br>
<span class="HOEnZb"><font color="#888888">--<br>
1.9.1<br>
<br>
</font></span></blockquote></div><br></div>