[Xen-devel] RE: [PATCH][libxc] Bounds check for parray

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject:	[Xen-devel] RE: [PATCH][libxc] Bounds check for parray
From:	"Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date:	Sun, 21 May 2006 17:57:46 -0400
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Sun, 21 May 2006 14:58:16 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
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:	AcZ9CV/My3N3+aeEQ5SJW9lIkKC43gAF+eKA
Thread-topic:	[PATCH][libxc] Bounds check for parray

> I added a couple extra sanity checks to parseelfimage which should
make
> this patch unnecessary:
>   1. Ensure VIRT_BASE is specified if ELF_PADDR_OFFSET is specified.
>   2. Ensure that VIRT_BASE is less than kernel virtual load address.

I did a few tests and everything seems to be fine now. I am not able to
get the builder to segfault. Hopefully this has been laid to rest now
:-).

Thanks,
Aravindh

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] RE: [PATCH][libxc] Bounds check for parray