From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/15408] procfs probes broken on rawhide
Date: Tue, 07 May 2013 15:40:00 -0000 [thread overview]
Message-ID: <bug-15408-6586-BHO7MYJmMv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15408-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15408
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> 2013-05-07 15:40:34 UTC ---
Then this sounds a little like bug #14223, wherein kernel permission checks are
naive to the extent that they perform this work not at the user-kernel
interface, but several layers down within the kernel (which is sort of
setuid-root already).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-05-07 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 17:22 [Bug runtime/15408] New: " dsmith at redhat dot com
2013-04-26 17:28 ` [Bug runtime/15408] " dsmith at redhat dot com
2013-04-30 16:25 ` dsmith at redhat dot com
2013-05-02 16:04 ` dsmith at redhat dot com
2013-05-07 15:38 ` dsmith at redhat dot com
2013-05-07 15:40 ` fche at redhat dot com [this message]
2013-05-07 16:32 ` dsmith at redhat dot com
2013-05-07 21:23 ` dsmith at redhat dot com
2013-05-09 23:10 ` jistone at redhat dot com
2013-05-10 14:10 ` 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-15408-6586-BHO7MYJmMv@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).