xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
	<xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>, Jan Beulich <jbeulich@suse.com>,
	Ian Jackson <ian.jackson@citrix.com>
Subject: Re: [PATCH for-4.15 6/7] CHANGELOG.md: Various entries, mostly xenstore
Date: Thu, 1 Apr 2021 15:00:35 +0100	[thread overview]
Message-ID: <97d317fb-16d7-a14e-e74e-62fa83159838@citrix.com> (raw)
In-Reply-To: <20210401133827.362216-6-george.dunlap@citrix.com>

On 01/04/2021 14:38, George Dunlap wrote:
> ...grouped by submitters / maintainers
>
> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
> ---
> CC: Juergen Gross <jgross@suse.com>
> CC: Jan Beulich <jbeulich@suse.com>
> CC: Ian Jackson <ian.jackson@citrix.com>
> ---
>  CHANGELOG.md | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index 2f26cd5c87..9c272a0113 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -28,8 +28,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>   - Factored out HVM-specific shadow code, improving code clarity and reducing the size of PV-only hypervisor builds
>   - Added XEN_SCRIPT_DIR configuration option to specify location for Xen scripts, rather than hard-coding /etc/xen/scripts
>   - xennet: Documented a way for the backend (or toolstack) to specify MTU to the frontend
> + - Fix permissions for watches on @introduceDomain and @releaseDomain: By default, only privileged domains can set watches; but specific domains can be given permission in order to allow disaggregation.

This is XSA-115, and isn't something new in 4.15 vs 4.14.  (I think?)

> + - xenstore can now be live-updated on a running system.

This needs to be very clear that it is tech preview.  It does not
currently work cleanly if a malicious VM deliberately holds a
transaction open.

~Andrew


  parent reply	other threads:[~2021-04-01 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 13:38 [PATCH for-4.15 1/7] CHANGELOG.md: Mention XEN_SCRIPT_DIR George Dunlap
2021-04-01 13:38 ` [PATCH for-4.15 2/7] CHANGELOG.md: xl PCI configuration doc, xenstore MTU entries George Dunlap
2021-04-01 15:30   ` Paul Durrant
2021-04-01 13:38 ` [PATCH for-4.15 3/7] CHANGELOG.md: Some additional affordances in various xl subcommands George Dunlap
2021-04-01 13:38 ` [PATCH for-4.15 4/7] CHANGELOG.md: Mention various ARM errata George Dunlap
2021-04-01 14:13   ` Jan Beulich
2021-04-01 16:14     ` Julien Grall
2021-04-01 13:38 ` [PATCH for-4.15 5/7] CHANGELOG.md: Various new entries, mostly x86 George Dunlap
2021-04-01 14:13   ` Jan Beulich
2021-04-01 13:38 ` [PATCH for-4.15 6/7] CHANGELOG.md: Various entries, mostly xenstore George Dunlap
2021-04-01 13:54   ` Juergen Gross
2021-04-01 14:00   ` Andrew Cooper [this message]
2021-04-01 14:13     ` George Dunlap
2021-04-01 14:16       ` Andrew Cooper
2021-04-01 14:45         ` George Dunlap
2021-04-01 13:38 ` [PATCH for-4.15 7/7] CHANGELOG.md: irq-max-guests George Dunlap
2021-04-01 14:17   ` Jan Beulich
2021-04-01 14:46     ` George Dunlap
2021-04-06 16:31 ` [PATCH for-4.15 1/7] CHANGELOG.md: Mention XEN_SCRIPT_DIR Ian Jackson

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=97d317fb-16d7-a14e-e74e-62fa83159838@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /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;
as well as URLs for NNTP newsgroup(s).