public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/27224] stap 4.4 'cannot attach to module' in debugfs mode as non-root (WITH WORKAROUND)
Date: Fri, 29 Jan 2021 10:43:18 +0000	[thread overview]
Message-ID: <bug-27224-6586-rGN98ULHw7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27224-6586@http.sourceware.org/bugzilla/>

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

Craig Ringer <craig.ringer at 2ndquadrant dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|WAITING                     |RESOLVED

--- Comment #6 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
That's

```
commit e3d03db82
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Sun Dec 13 21:05:23 2020 -0500

    PR23512: fix staprun/stapio operation via less-than-root privileges

    Commit 7615cae790c899bc8a82841c75c8ea9c6fa54df3 for PR26665 introduced
    a regression in handling stapusr/stapdev/stapsys gid invocation of
    staprun/stapio.  This patch simplifies the relevant code in
    staprun/ctl.c, init_ctl_channel(), to rely on openat/etc. to populate
    and use the relay_basedir_fd as much as possible.  Also, we now avoid
    unnecessary use of access(), which was checking against the wrong
    (real rather than effective) uid/gid.
```

and sounds about right.

Fine to close this. Workaround is documented by this bug now.

*** This bug has been marked as a duplicate of bug 27067 ***

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

      parent reply	other threads:[~2021-01-29 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  4:26 [Bug runtime/27224] New: stap 4.4 'cannot attach to module' in debugfs mode as non-root craig.ringer at 2ndquadrant dot com
2021-01-22  4:26 ` [Bug runtime/27224] " craig.ringer at 2ndquadrant dot com
2021-01-22  4:27 ` craig.ringer at 2ndquadrant dot com
2021-01-22  4:31 ` craig.ringer at 2ndquadrant dot com
2021-01-22  4:42 ` craig.ringer at 2ndquadrant dot com
2021-01-22  4:42 ` [Bug runtime/27224] stap 4.4 'cannot attach to module' in debugfs mode as non-root (WITH WORKAROUND) craig.ringer at 2ndquadrant dot com
2021-01-22 22:30 ` fche at redhat dot com
2021-01-22 22:31 ` fche at redhat dot com
2021-01-29 10:43 ` craig.ringer at 2ndquadrant dot com [this message]

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-27224-6586-rGN98ULHw7@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).