diff --git a/libcgroup-0.41-api.c-fix-order-of-memory-subsystem-parameters.patch b/libcgroup-0.41-api.c-fix-order-of-memory-subsystem-parameters.patch
new file mode 100644
index 0000000..9700530
--- /dev/null
+++ b/libcgroup-0.41-api.c-fix-order-of-memory-subsystem-parameters.patch
@@ -0,0 +1,66 @@
+From 72a9e0c3d4f8daca9f7dc389edbc1013d7c0d808 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Nikola=20Forr=C3=B3?= <nforro@redhat.com>
+Date: Fri, 8 Apr 2016 17:00:19 +0200
+Subject: [PATCH] api.c: fix order of memory subsystem parameters generated by
+ cgsnapshot
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Order of parameters usually doesn't matter, but that's not the case with
+memory.limit_in_bytes and memory.memsw.limit_in_bytes. When the latter
+is first in the list of parameters, the resulting configuration is not
+loadable with cgconfigparser.
+
+This happens because when a cgroup is created, both memory.limit_in_bytes
+and memory.memsw.limit_in_bytes parameters are initialized to highest
+value possible (RESOURCE_MAX). And because memory.memsw.limit_in_bytes
+must be always higher or equal to memory.limit_in_bytes, it's impossible
+to change its value first.
+
+Make sure that after constructing parameter list of memory subsystem,
+the mentioned parameters are in correct order.
+
+Signed-off-by: Nikola Forró <nforro@redhat.com>
+---
+ src/api.c | 24 ++++++++++++++++++++++++
+ 1 file changed, 24 insertions(+)
+
+diff --git a/src/api.c b/src/api.c
+index 0bf0615..f5da553 100644
+--- a/src/api.c
++++ b/src/api.c
+@@ -2651,6 +2651,30 @@ int cgroup_get_cgroup(struct cgroup *cgroup)
+ 			}
+ 		}
+ 		closedir(dir);
++
++		if (! strcmp(cgc->name, "memory")) {
++			/*
++			 * Make sure that memory.limit_in_bytes is placed before
++			 * memory.memsw.limit_in_bytes in the list of values
++			 */
++			int memsw_limit = -1;
++			int mem_limit = -1;
++
++			for (j = 0; j < cgc->index; j++) {
++				if (! strcmp(cgc->values[j]->name,
++								"memory.memsw.limit_in_bytes"))
++					memsw_limit = j;
++				else if (! strcmp(cgc->values[j]->name,
++									"memory.limit_in_bytes"))
++					mem_limit = j;
++			}
++
++			if (memsw_limit >= 0 && memsw_limit < mem_limit) {
++				struct control_value *val = cgc->values[memsw_limit];
++				cgc->values[memsw_limit] = cgc->values[mem_limit];
++				cgc->values[mem_limit] = val;
++			}
++		}
+ 	}
+ 
+ 	/* Check if the group really exists or not */
+-- 
+2.4.11
+
diff --git a/libcgroup.spec b/libcgroup.spec
index 730a58a..5c044d7 100644
--- a/libcgroup.spec
+++ b/libcgroup.spec
@@ -5,7 +5,7 @@
 Summary: Library to control and monitor control groups
 Name: libcgroup
 Version: 0.41
-Release: 8%{?dist}
+Release: 9%{?dist}
 License: LGPLv2+
 Group: Development/Libraries
 URL: http://libcg.sourceforge.net/
@@ -19,6 +19,8 @@ Patch3: libcgroup-0.40.rc1-fread.patch
 Patch4: libcgroup-0.40.rc1-templates-fix.patch
 Patch5: libcgroup-0.41-lex.patch
 Patch6: libcgroup-0.41-api.c-support-for-setting-multiline-values-in-contro.patch
+# resolves #1348874
+Patch7: libcgroup-0.41-api.c-fix-order-of-memory-subsystem-parameters.patch
 
 BuildRequires: byacc, coreutils, flex, pam-devel, systemd-units
 Requires(pre): shadow-utils
@@ -67,6 +69,7 @@ provide scripts to manage that configuration.
 %patch4 -p1 -b .templates-fix
 %patch5 -p2 -b .lex
 %patch6 -p1
+%patch7 -p1
 
 %build
 %configure --enable-pam-module-dir=%{_libdir}/security \
@@ -167,6 +170,10 @@ getent group cgred >/dev/null || groupadd -r cgred
 %{_libdir}/pkgconfig/libcgroup.pc
 
 %changelog
+* Fri Jul 01 2016 Nikola Forró <nforro@redhat.com> - 0.41-9
+- resolves: #1348874
+  api.c: fix order of memory subsystem parameters generated by cgsnapshot
+
 * Thu Feb 04 2016 Fedora Release Engineering <releng@fedoraproject.org> - 0.41-8
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild