public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: Re: [PATCH guest-common] fix #2834: skip refs in config_with_pending_array
Date: Sat, 11 Jul 2020 18:49:16 +0200	[thread overview]
Message-ID: <f12f01b7-053c-850b-bb4e-8c21c1ca6f7d@proxmox.com> (raw)
In-Reply-To: <20200710181128.30097-1-s.ivanov@proxmox.com>

On 10.07.20 20:11, Stoiko Ivanov wrote:
> With the refactoring of config_with_pending_array in
> daf8fca57a34417365c873ed91f3a52bf0002a4f a few sanity checks on parsed configs
> were dropped.
> 
> One case where a config value should be skipped, instead of parsed and added
> is when the value is not scalar. This is the case for the raw lxc keys
> (e.g. lxc.init.cmd, lxc.apparmor.profile) - which get added as array to the
> 'lxc' key.
> 
> This patch reintroduces the skipping of non-scalar values, when parsing the
> config but not for the pending values.
> From a short look through the commit history the sanity checks were in place
> since 2014 (introduced in qemu-server for handling pending configuration
> changes), and their removal did not cause any other regressions.
> To my knowledge only the raw lxc config keys are parsed into a non-scalar
> value.
> 
> Tested by adding a 'lxc.init.cmd' key to a container config.
> 
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> I hope that I did not miss another case where the sanity-checks are necessary,
> and can gladly send a v2 reintroducing all of them.
> 
>  PVE/GuestHelpers.pm | 2 ++
>  1 file changed, 2 insertions(+)
> 
>

applied, many thanks! Added a comment as followup, as during the refactoring Oguz had
some feeling that there was something else besides snapshots but could not come
up with anything, so I've thrown it out. Vetter safe than sorry (twice).




      reply	other threads:[~2020-07-11 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 18:11 [pve-devel] " Stoiko Ivanov
2020-07-11 16:49 ` Thomas Lamprecht [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=f12f01b7-053c-850b-bb4e-8c21c1ca6f7d@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.ivanov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal