public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15456] New: syscalls and nd_syscalls tapset compat probe points broken on kernel 3.10
Date: Fri, 10 May 2013 18:02:00 -0000	[thread overview]
Message-ID: <bug-15456-6586@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 15456
           Summary: syscalls and nd_syscalls tapset compat probe points
                    broken on kernel 3.10
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap@sourceware.org
        ReportedBy: dsmith@redhat.com
    Classification: Unclassified


In kernel 3.10 (3.10.0-0.rc0.git21.1.fc20.x86_64), the compat syscalls have
been cleaned up and arguments named "first", "second", etc. have been renamed
to have more meaning. The syscalls and nd_syscalls tapsets need to be updated
to handle this change. In addition, the compat syscall probes should try to
have convenience variables named like the non-compat syscall probes.

Here's an example:

====
# stap -ve 'probe syscall.compat_sys_semctl { printf("%s(%s)\n", name, argstr)
}'
Pass 1: parsed user script and 90 library script(s) using
167752virt/25572res/2172shr/24084data kb, in 180usr/40sys/215real ms.
semantic error: unable to find local 'first', [man error::dwarf] dieoffset
0x2229dc1 in kernel, near pc 0xffffffff812d09e0 in compat_SyS_semctl
ipc/compat.c (alternatives: $semid $semnum $cmd $arg): identifier '$first' at
/usr/local/share/systemtap/tapset/linux/syscalls2.stp:1534:37
        source:     argstr = sprintf("%d, %d, %d, %p", $first, $second, $third,
$uptr)
                                                       ^

Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 0 global(s)
using 364288virt/164648res/105504shr/59792data kb, in 1000usr/790sys/1807real
ms.
Pass 2: analysis failed.  [man error::pass2]
====

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

             reply	other threads:[~2013-05-10 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 18:02 dsmith at redhat dot com [this message]
2013-05-10 19:41 ` [Bug tapsets/15456] " dsmith 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-15456-6586@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).