From: Oguz Bektas <o.bektas@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH lxc 0/2] bump to 4.0.4
Date: Mon, 14 Sep 2020 14:56:02 +0200 [thread overview]
Message-ID: <20200914125602.GA388711@gaia.proxmox.com> (raw)
In-Reply-To: <20200910124050.23874-1-s.ivanov@proxmox.com>
didnt find any other problems besides the mount issue with ext4
Tested-by: Oguz Bektas <o.bektas@proxmox.com>
On Thu, Sep 10, 2020 at 02:40:48PM +0200, Stoiko Ivanov wrote:
> this patchset updates lxc to 4.0.4
>
> tested on my system and a virtual ceph-cluster (for ha and migration tests),
> created some backups of containers. - everything seems to work fine.
>
> Stoiko Ivanov (2):
> update upstream to 4.0.4 and rebase patches
> bump version to 4.0.4-1
>
> debian/changelog | 6 +++++
> ...ning-lxc-monitord-as-a-system-daemon.patch | 4 +--
> ...roup.dir.-monitor-container-containe.patch | 8 +++---
> ....container.namespace-lxc.cgroup.cont.patch | 2 +-
> ...dd-and-document-cgroup_advanced_isol.patch | 14 +++++-----
> ...up.dir.-monitor-container-container..patch | 2 +-
> ...09-cgroups-adhere-to-boolean-return.patch} | 4 +--
> ...the-right-path-in-get_cgroup-command.patch | 25 ------------------
> ...rvice-start-after-a-potential-syslo.patch} | 0
> ...ig-deny-rw-mounting-of-sys-and-proc.patch} | 0
> ...PVE-Config-attach-always-use-getent.patch} | 8 +++---
> ...apparmor-Allow-ro-remount-of-boot_id.patch | 26 -------------------
> debian/patches/series | 10 +++----
> lxc | 2 +-
> 14 files changed, 32 insertions(+), 79 deletions(-)
> rename debian/patches/pve/{0010-cgroups-adhere-to-boolean-return.patch => 0009-cgroups-adhere-to-boolean-return.patch} (90%)
> delete mode 100644 debian/patches/pve/0009-get-the-right-path-in-get_cgroup-command.patch
> rename debian/patches/pve/{0011-PVE-Config-lxc.service-start-after-a-potential-syslo.patch => 0010-PVE-Config-lxc.service-start-after-a-potential-syslo.patch} (100%)
> rename debian/patches/pve/{0012-PVE-Config-deny-rw-mounting-of-sys-and-proc.patch => 0011-PVE-Config-deny-rw-mounting-of-sys-and-proc.patch} (100%)
> rename debian/patches/pve/{0013-PVE-Config-attach-always-use-getent.patch => 0012-PVE-Config-attach-always-use-getent.patch} (89%)
> delete mode 100644 debian/patches/pve/0014-apparmor-Allow-ro-remount-of-boot_id.patch
>
> --
> 2.20.1
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
prev parent reply other threads:[~2020-09-14 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 12:40 Stoiko Ivanov
2020-09-10 12:40 ` [pve-devel] [PATCH lxc 1/2] update upstream to 4.0.4 and rebase patches Stoiko Ivanov
2020-09-10 12:40 ` [pve-devel] [PATCH lxc 2/2] bump version to 4.0.4-1 Stoiko Ivanov
2020-09-14 12:56 ` Oguz Bektas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200914125602.GA388711@gaia.proxmox.com \
--to=o.bektas@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.