xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xensource.com, security@xenproject.org,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] libxl: Fix NULL pointer due to XSA-178 fix wrong XS nodename
Date: Wed, 8 Jun 2016 16:18:02 +0100	[thread overview]
Message-ID: <22360.14122.52050.599800@mariner.uk.xensource.com> (raw)
In-Reply-To: <20160608151136.GB28116@citrix.com>

Wei Liu writes ("Re: [PATCH] libxl: Fix NULL pointer due to XSA-178 fix wrong XS nodename"):
> Reviewed-by: Wei Liu <wei.liu2@citrix.com>

Thanks.  As per discussion on irc, I have now pushed this to all the
affected branches.

I think we should issue an update to XSA-178.  Given that we warned in
the advisory that the XSA-178 patches were being tested, I think we
can afford to wait until we see another set of test results.


Xen-devel mailing list

      reply	other threads:[~2016-06-08 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 14:56 [PATCH] libxl: Fix NULL pointer due to XSA-178 fix wrong XS nodename Ian Jackson
2016-06-08 15:11 ` Wei Liu
2016-06-08 15:18   ` Ian Jackson [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22360.14122.52050.599800@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=security@xenproject.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xensource.com \


* 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).