| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] Sysenter_entry and /proc/kallsyms |
| From: | Steve Brueckner <steve@xxxxxxxxxxxxxx> |
| Date: | 2006年7月27日 17:52:23 -0400 |
| Delivery-date: | 2006年7月27日 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> |
|---|---|---|
| ||
| Previous by Date: | RE: [Xen-devel] RFC: virtual network access control , Caitlin Bestler |
|---|---|
| Next by Date: | Re: [Xen-devel] [RESEND] Question about recursive mappings , Bruce Rogers |
| Previous by Thread: | [Xen-devel] RFC: virtual network access control , Reiner Sailer |
| Next by Thread: | Re: [Xen-devel] Sysenter_entry and /proc/kallsyms , Jan Beulich |
| Indexes: | [Date] [Thread] [Top] [All Lists] |