WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [Xen-staging] [xen-unstable] ia64, ppc: Remove uses

To: Alex Williamson <alex.williamson@xxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-staging] [xen-unstable] ia64, ppc: Remove uses of sprintf().
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 30 Jan 2007 17:35:45 +0000
Cc: Christoph Egger <Christoph.Egger@xxxxxxx>
Delivery-date: Tue, 30 Jan 2007 09:35:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1170176582.10792.101.camel@bling>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdElRI6UQDXk7CIEduv7gANk04WTA==
Thread-topic: [Xen-devel] Re: [Xen-staging] [xen-unstable] ia64, ppc: Remove uses of sprintf().
User-agent: Microsoft-Entourage/11.3.3.061214
On 30/1/07 5:03 pm, "Alex Williamson" <alex.williamson@xxxxxx> wrote:

>    What's the purpose of all this "cleanup"?  This is just munging files
> that we're leveraging from Linux, making updating them later on more
> difficult.  And these really should have been submitted via the
> xen-ia64-devel list.

The aim is to get rid of the 'dangerous' sprintf/strcat/strcpy functions.
Obviously not all uses are unsafe but if we don't define them then dangerous
uses can't creep in. There were already a few uses throughout Xen where
overflow might have silently become a possibility in future (although none
would be obviously exploitable). On the x86 side at least it turned out that
only a few Linux-derived lines of code had to be modified which seems an
acceptable price to pay.

If you still need those functions (do you still grab and munge a whole Linux
tree to make Xen on ia64?) then you can define them just for ia64/linux-xen
to provide a Linux-y environment, in which case it would make sense to
revert any removal patches applied in that subtree.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>