public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "adrien at kunysz dot be" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/12596] New: blacklist is too broad (raw_.*)
Date: Sun, 20 Mar 2011 00:35:00 -0000	[thread overview]
Message-ID: <bug-12596-6586@http.sourceware.org/bugzilla/> (raw)

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

           Summary: blacklist is too broad (raw_.*)
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: minor
          Priority: P2
         Component: translator
        AssignedTo: systemtap@sourceware.org
        ReportedBy: adrien@kunysz.be


As reported by dpward on IRC, some functions that have no obvious reason to be
blacklisted are "hidden" by the "raw_.*" regular expression. Most notably, the
raw_sendmsg@net/ipv4/raw.c function is not accessible outside of guru mode. A
quick grep of /proc/kallsyms shows other possible casualties, the most obvious
ones being in the following files:

drivers/char/raw.c
net/ieee802154/raw.c
net/ipv4/raw.c
net/can/raw.c

The "raw_.*" filter seems to be targeted at locks but it doesn't specify which
ones so how to fix this properly isn't immediately obvious (to me).

-- 
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:[~2011-03-20  0:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20  0:35 adrien at kunysz dot be [this message]
2011-03-20  0:37 ` [Bug translator/12596] " adrien at kunysz dot be
2016-05-26 17:57 ` fche 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-12596-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).