public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* Strange stap error...
@ 2009-12-19 17:45 Steve Dickson
  2009-12-19 21:41 ` Mark Wielaard
  2009-12-20 20:29 ` Frank Ch. Eigler
  0 siblings, 2 replies; 3+ messages in thread
From: Steve Dickson @ 2009-12-19 17:45 UTC (permalink / raw)
  To: SystemTAP

I'm getting the following error:

$ sudo ~/bin/stap -g inode_permission.stp 
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
Copy failed ("/tmp/stapwUrw9k/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko" to "/home/steved/.systemtap/cache/f6/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko"): No such file or directory
ERROR: Unable to canonicalize path "/tmp/stapwUrw9k/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko": No such file or directory
Retrying, after attempted removal of module stap_f69367bbfe0f310d5472acdca1010f45_2000 (rc -1)
ERROR: Unable to canonicalize path "/tmp/stapwUrw9k/stap_f69367bbfe0f310d5472acdca1010f45_2000.ko": No such file or directory
Pass 5: run failed.  Try again with another '--vp 00001' option.

Using the following version of stap (straight out of the git tree)
 
$ ~/bin/stap -V
SystemTap translator/driver (version 1.0/0.143 commit release-1.0-390-g39b375a)
Copyright (C) 2005-2009 Red Hat, Inc. and others
This is free software; see the source for copying conditions.

Using a relativity new kernel...

$ uname -a
Linux redhat 2.6.32-2.nfs41.el6.x86_64.debug #1 SMP Fri Dec 18 08:42:45 EST 2009 x86_64 GNU/Linux


With the following tap script

$ cat inode_permission.stp 
probe kernel.function("inode_permission")
{
	printf("inode_permission: inode %p mask 0x%x\n", $inode, $mask);
}
probe kernel.function("inode_permission").return
{
	printf("  inode_permission: return %d\n", $return);
}

probe begin { log("inode_permission probe") }
probe end { log("inode_permission probe") }


any ideas?

steved.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Strange stap error...
  2009-12-19 17:45 Strange stap error Steve Dickson
@ 2009-12-19 21:41 ` Mark Wielaard
  2009-12-20 20:29 ` Frank Ch. Eigler
  1 sibling, 0 replies; 3+ messages in thread
From: Mark Wielaard @ 2009-12-19 21:41 UTC (permalink / raw)
  To: Steve Dickson; +Cc: SystemTAP

Hi Steve,

On Sat, 2009-12-19 at 12:45 -0500, Steve Dickson wrote:
> I'm getting the following error:
> 
> $ sudo ~/bin/stap -g inode_permission.stp 
> gpg: no default secret key: No secret key
> gpg: signing failed: No secret key
> [...]
> Using a relativity new kernel...
> 
> $ uname -a
> Linux redhat 2.6.32-2.nfs41.el6.x86_64.debug #1 SMP Fri Dec 18 08:42:45 EST 2009 x86_64 GNU/Linux

Looks like your kernel-devel package wants to produce signed modules but
gpg doesn't know what signature to use. You might get some more
information when using stap -vp 00004 (add 4 to verbose for pass 5,
which is the compile step).

Cheers,

Mark

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Strange stap error...
  2009-12-19 17:45 Strange stap error Steve Dickson
  2009-12-19 21:41 ` Mark Wielaard
@ 2009-12-20 20:29 ` Frank Ch. Eigler
  1 sibling, 0 replies; 3+ messages in thread
From: Frank Ch. Eigler @ 2009-12-20 20:29 UTC (permalink / raw)
  To: Steve Dickson; +Cc: SystemTAP

Steve Dickson <SteveD@redhat.com> writes:

> I'm getting the following error:
> [...]
> Using a relativity new kernel...
> $ uname -a
> Linux redhat 2.6.32-2.nfs41.el6.x86_64.debug #1 SMP Fri Dec 18 08:42:45 EST 2009 x86_64 GNU/Linux
> [...]

https://bugzilla.redhat.com/show_bug.cgi?id=543529
(RHEL6 kernel-devel bug in module signing patches).

It seems possible to work around this with recent stap using

 # stap -BCONFIG_MODULE_SIG=n   [...other options...]

- FChE

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-12-20 20:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-12-19 17:45 Strange stap error Steve Dickson
2009-12-19 21:41 ` Mark Wielaard
2009-12-20 20:29 ` Frank Ch. Eigler

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).