All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henry Wang <Henry.Wang@arm.com>
To: Anthony PERARD <anthony.perard@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: RE: [PATCH 1/2] tools/libxl: Fixes to libxl__domain_set_paging_mempool_size()
Date: Mon, 21 Nov 2022 15:16:36 +0000	[thread overview]
Message-ID: <AS8PR08MB79914380261A37B7EF8F0955920A9@AS8PR08MB7991.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <Y3uPFV6wszfgD4Id@perard.uk.xensource.com>

Hi Andrew,

> -----Original Message-----
> Subject: Re: [PATCH 1/2] tools/libxl: Fixes to
> libxl__domain_set_paging_mempool_size()
> 
> On Mon, Nov 21, 2022 at 02:37:30PM +0000, Andrew Cooper wrote:
> > The error message accidentally printed the bytes value as if it were kB.
> >
> > Furthermore, both b_info.shadow_memkb and shadow_mem are uint64_t,
> meaning
> > there is a risk of overflow if the user specified a stupidly large value in
> > the vm.cfg file.  Check and reject such a condition.
> >
> > Fixes: 7c3bbd940dd8 ("xen/arm, libxl: Revert XEN_DOMCTL_shadow_op;
> use p2m mempool hypercalls")
> > Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > ---
> >
> > v2:
> >  * Retain PRIu64
> >  * Check for overflow
> >
> > For 4.17.  This is a low risk change, removes one overflow case, and makes
> an
> > error message accurate.
> 
> Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>

Release-acked-by: Henry Wang <Henry.Wang@arm.com>

Kind regards,
Henry


  reply	other threads:[~2022-11-21 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 14:37 [PATCH for-4.17 0/2] Even more XSA-409 fixes Andrew Cooper
2022-11-21 14:37 ` [PATCH 1/2] tools/libxl: Fixes to libxl__domain_set_paging_mempool_size() Andrew Cooper
2022-11-21 14:45   ` Anthony PERARD
2022-11-21 15:16     ` Henry Wang [this message]
2022-11-21 14:37 ` [PATCH 2/2] xen/flask: Wire up XEN_DOMCTL_{get,set}_paging_mempool_size Andrew Cooper
2022-11-21 15:18   ` Henry Wang
2022-11-21 15:39   ` Jason Andryuk
2022-11-21 15:46     ` Andrew Cooper
2022-11-21 15:54       ` Jason Andryuk
2022-11-21 16:07   ` Daniel P. Smith

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=AS8PR08MB79914380261A37B7EF8F0955920A9@AS8PR08MB7991.eurprd08.prod.outlook.com \
    --to=henry.wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.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 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.