From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-13394-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 28395 invoked by alias); 3 Sep 2009 21:05:21 -0000
Received: (qmail 28355 invoked by uid 48); 3 Sep 2009 21:05:08 -0000
Date: Thu, 03 Sep 2009 21:05:00 -0000
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20090903210508.10601.fche@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug runtime/10601] New: user-space deref/registers in loc2c
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2009-q3/txt/msg00545.txt.bz2

For secure/robust memory and register access for user-space $target expressions,
the translator must parametrize loc2c to emit different calls for user-space
probes than for kernel-space ones.  This is partly so that user-space $pointers
can't poke at kernel memories, and vice versa.

Related, the user-space register/memory access logic must become aware of
32-bit vs. 64-bit user-space processes on a 64-bit host.  For registers,
this appears to require use of the proper utrace regset machinery instead
of poking at pt_regs.

-- 
           Summary: user-space deref/registers in loc2c
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10601

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.