public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jiri.horky at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/15101] [PATCH] Stap sefaults when calling NSS_shutdown() which was not previously initialized
Date: Thu, 07 Feb 2013 08:19:00 -0000	[thread overview]
Message-ID: <bug-15101-6586-PZDUq5fZVX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15101-6586@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Jiri Horky <jiri.horky at gmail dot com> 2013-02-07 08:19:20 UTC ---
Hi all,

I confirm that the latest git version fixes the problem  for us. As of
authorship, I would prefer if Lukas was listed as he was the one who found the
cause of segfault and fixed it.

Just to complete the picture, here are the requested information (without -vvvv
output of stap - I would have to downgrade stap and I understood it is no
longer necessary):

root@fe6.du1 ~/systemtap # rpm -qa | grep nss
nss_ldap-262-11.32.31.1
php5-openssl-5.2.14-0.7.30.42.1
libopenssl1_0_0-1.0.0c-18.21.1
insserv-1.12.0-25.3.20
libnsssharedhelper0-1.0.6-1.6
openssl-certs-0.9.8h-27.5.1
openssl-0.9.8j-0.44.1
libopenssl0_9_8-0.9.8j-0.44.1
libnsssharedhelper0-32bit-1.0.6-1.6
libopenssl0_9_8-32bit-0.9.8j-0.44.1
openssh-5.1p1-41.55.1.hpn4
mozilla-nss-32bit-3.13.5-0.4.2
openssh-askpass-5.1p1-41.55.1.hpn4
mozilla-nss-3.13.5-0.4.2

root@fe6.du1 ~/systemtap # rpm -qa | grep nspr
mozilla-nspr-32bit-4.9.1-0.5.1
mozilla-nspr-4.9.1-0.5.1

The stap was invoked normally just as:
stap -v -g /cxfs/clusterbase/admin/accounting/nfsdacc-fullpath.stp

One needs to have a patched nfsd tapset script to be able to use the
"nfsdacc-fullpath.stp" script:


--- tapset/linux/nfsd.stp       2013-01-04 21:22:00.718422707 +0100
+++ tapset/linux/nfsd.stp-lh    2013-01-04 21:10:50.328889987 +0100
@@ -536,6 +536,8 @@
        vec = $rqstp->rq_vec
        vlen = $write->wr_vlen
        stable = $write->wr_stable_how
+       uid = $rqstp->rq_cred->cr_uid;
+       gid = $rqstp->rq_cred->cr_gid;

        name = "nfsd.proc4.write"
        argstr = sprintf("%d,%d",count,offset)

Thank you
Jiri Horky

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2013-02-07  8:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 14:21 [Bug dyninst/15101] New: " jiri.horky at gmail dot com
2013-02-05 14:22 ` [Bug dyninst/15101] " jiri.horky at gmail dot com
2013-02-05 14:23 ` jiri.horky at gmail dot com
2013-02-05 15:09 ` brolley at redhat dot com
2013-02-05 17:19 ` [Bug server/15101] " jistone at redhat dot com
2013-02-06 18:21 ` fche at redhat dot com
2013-02-06 18:23 ` fche at redhat dot com
2013-02-06 21:01 ` fche at redhat dot com
2013-02-06 21:42 ` brolley at redhat dot com
2013-02-06 21:43 ` brolley at redhat dot com
2013-02-07  3:58 ` fche at redhat dot com
2013-02-07  8:19 ` jiri.horky at gmail dot com [this message]
2013-02-08 18:13 ` brolley at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15101-6586-PZDUq5fZVX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).