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

[Xen-devel] Sysenter_entry and /proc/kallsyms

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Sysenter_entry and /proc/kallsyms
From: Steve Brueckner <steve@xxxxxxxxxxxxxx>
Date: Thu, 27 Jul 2006 17:52:23 -0400
Delivery-date: Thu, 27 Jul 2006 14:53:07 -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
I notice that sysenter_entry is not present in /proc/kallsyms for Xen
kernels, but is present in my non-Xen FC5 kernel.  I'm doing some security
research and trying to install an LKM rootkit into a paravirtualized VM, but
it's trying to look up sysenter_entry during compile and failing.

Can anyone explain why sysenter_entry is missing from the table, keeping in
mind I'm a kernel neophyte?

Thanks,

 - Steve

Steve Brueckner, ATC-NY

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

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