summaryrefslogtreecommitdiffstats
path: root/recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2018-05-31 17:08:04 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2018-06-03 23:26:51 -0400
commit0d7cfe86600b0306af97578b16ec7ca264ea1346 (patch)
tree64c2f8eb8285a75592a6c657691d113525335e44 /recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch
parent4987f02577432e518e627c2c139c378b8b6a9678 (diff)
downloadmeta-virtualization-0d7cfe86600b0306af97578b16ec7ca264ea1346.tar.gz
lxc: uprev to v3.0.0
Update to the latest lxc release. This requires some minor patch updates (fuzz and offset, not content) along with dropping a no longer needed fix for gcc7 (gcc 7.3 is everywhere and is patched). The ptests were already busted before the uprev so I was not able to run them but I will follow up with a fix for this. I did run against our usual usecases 'lxc-create', 'lxc-console', 'lxc-ls', 'lxc-destroy', 'lxc-start', 'lxc-execute', 'lxc-attach'... and there were no issues (outcomes matched v2.0.8). Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch')
-rw-r--r--recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch34
1 files changed, 0 insertions, 34 deletions
diff --git a/recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch b/recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch
deleted file mode 100644
index 90740fb3..00000000
--- a/recipes-containers/lxc/files/cgroups-work-around-issue-in-gcc-7.patch
+++ /dev/null
@@ -1,34 +0,0 @@
1From 58a2d817a82100d287c60c63315d81445cdba3f9 Mon Sep 17 00:00:00 2001
2From: Mark Asselstine <mark.asselstine@windriver.com>
3Date: Thu, 15 Jun 2017 15:12:08 -0400
4Subject: [PATCH] cgroups: work around issue in gcc 7
5
6This works around
7https://bugzilla.yoctoproject.org/show_bug.cgi?id=11672
8https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
9
10By removing a single cgroup entry. For the majority of usecases this
11loss of a single entry should not be an issue and once gcc 7 is fixed
12we can revert this.
13
14Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
15---
16 src/lxc/cgroups/cgfsng.c | 2 +-
17 1 file changed, 1 insertion(+), 1 deletion(-)
18
19diff --git a/src/lxc/cgroups/cgfsng.c b/src/lxc/cgroups/cgfsng.c
20index ebd548b..c520abd 100644
21--- a/src/lxc/cgroups/cgfsng.c
22+++ b/src/lxc/cgroups/cgfsng.c
23@@ -1373,7 +1373,7 @@ static inline bool cgfsng_create(void *hdata)
24 offset = cgname + len - 5;
25
26 again:
27- if (idx == 1000) {
28+ if (idx == 999) {
29 ERROR("Too many conflicting cgroup names");
30 goto out_free;
31 }
32--
332.7.4
34