public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/23512] New: regression in --privilege=stapusr operation
Date: Fri, 10 Aug 2018 23:40:00 -0000	[thread overview]
Message-ID: <bug-23512-6586@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=23512

            Bug ID: 23512
           Summary: regression in --privilege=stapusr operation
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
          Assignee: systemtap at sourceware dot org
          Reporter: fche at redhat dot com
  Target Milestone: ---

My commits for PR23160,PR14690 have caused a regression in the way
privilege-testing of elaboration of embedded-c tapset functions is handled. 
New code changes the timing at which the /* unprivileged */ type pragmas are
processed.  Now they can fail for functions like kernel_string() even though
they are not called, even transitively, from the end-user script.  This breaks
e.g. the unprivileged-myproc test cases.

It turns out we run symbol elaboration in an overly inclusive manner.  Any
function defined in a tapset file chosen for inclusion is fully processed, even
though it may not be transitively called at all.  This represents perhaps
considerable wasted translation effort, esp. considering expensive constructs
like @cast().  We should not spend any serious efforts processing parts of
tapsets that are not reachable from the end-user script.  This suggests the
resolve_syms pass must be iterative/relaxation-based, like the optimization
passes later on.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2018-08-10 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 23:40 fche at redhat dot com [this message]
2018-08-11 18:49 ` [Bug translator/23512] " agentzh at gmail dot com
2021-11-10  9:00 ` bankingservice2020 at gmail 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-23512-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).