From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [PATCH 0/6] libxl: config file string handling cleanups
Date: Tue, 7 Jul 2015 17:13:19 +0100
Message-ID: <1436285605-18411-1-git-send-email-ian.jackson@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

These 6 followup patches were developed during a review of the xl
string handling code, prompted by XSA-137.  They were embargoed until
today.

I have reviewed the whole of xl's string handling for other bugs.
My search terms included:
     realloc sn?printf str \bstr \bstrcpy \bstrn \bstrcat \bmemcpy
     \bmemchr \bp\b

Surprisingly, I found not too much untoward.

Of these only two are even backport candidates:

  xl: Do not ignore unparseable PCI BDFs
  xl: Rewrite trim()