Re: Systemtap results on power64 box against kernel version 2.6.36-rc1

[Mark Wielaard <mjw at redhat dot com>]

On Thu, 2010-08-19 at 09:25 -0700, Josh Stone wrote:
> On 08/19/2010 08:52 AM, Mark Wielaard wrote:
> > On Wed, 2010-08-18 at 12:00 +0530, divya wrote:
> >> FAIL: uprobeslibgcc-O3default-prelink-debug
> >> prelink ./libuprobeslibgcc-O3default-prelink-debug.so
> >> FAIL: uprobeslibgcc-O3default-prelink-sep-debug
> >> prelink ./libuprobeslibgcc-O3default-prelink-sep-debug.so
> >> FAIL: uprobeslibgcc-O3default-prelink-sep-debug-after
> >> prelink ./libuprobeslibgcc-O3default-prelink-sep-debug-after.so
> > 
> > This most likely means you don't have prelink installed, or it isn't
> > installed in the place the test expects. Could you check whether prelink
> > is installed on the machine and if so look in the systemtap.log to see
> > what is going wrong?
> > 
> 
> I've seen this failure in my VMs running from an NFS-mounted $HOME.  The
> details in my case are about security context:
> 
> Executing: /usr/sbin/prelink -vfNR -r 0x6400000
> ./libuprobeslibgcc-O3default-prelink-debug.so
> prelink failed: /usr/sbin/prelink: Could not set security context for
> ./libuprobeslibgcc-O3default-prelink-debug.so: Operation not supported
> FAIL: uprobeslibgcc-O3default-prelink-debug prelink
> ./libuprobeslibgcc-O3default-prelink-debug.so
> ... etc.

That does ring a bell. I believe prelink cannot work on nfs because it
tries to reset the selinux security context, but that is a fake
context...