From: Stephane Eranian <eranian@hpl.hp.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/16] 2.6.17-rc6 perfmon2 patch for review: new sysfs support
Date: Mon, 19 Jun 2006 06:36:26 -0700 [thread overview]
Message-ID: <20060619133626.GE25215@frankl.hpl.hp.com> (raw)
In-Reply-To: <200606172339_MC3-1-C2C6-D2C3@compuserve.com>
Chuck,
On Sat, Jun 17, 2006 at 11:36:36PM -0400, Chuck Ebbert wrote:
> In-Reply-To: <200606150907.k5F97YtU008130@frankl.hpl.hp.com>
>
> On Thu, 15 Jun 2006 02:07:34 -0700, Stephane Eranian wrote:
>
> > --- linux-2.6.17-rc6.orig/perfmon/perfmon_sysfs.c 1969-12-31 16:00:00.000000000 -0800
> > +++ linux-2.6.17-rc6/perfmon/perfmon_sysfs.c 2006-06-08 05:36:31.000000000 -0700
> ...
> > +struct pfm_controls pfm_controls = {
> > + .sys_group = PFM_GROUP_PERM_ANY,
> > + .task_group = PFM_GROUP_PERM_ANY,
> > + .arg_size_max = PAGE_SIZE,
> > + .smpl_buf_size_max = ~0,
> > +};
>
> This means that by default anyone can create monitoring sessions.
Yes.
> It should start out as restrictive as possible; the admin can relax
> permissions as needed.
>
I would expect distros to set it in a more restrictive way. That is what
I have observed with the Resources Limits such as RLIMIT_MEMLOCK, for instance.
I am not sure what the mainline policy is on this.
I am glad you looked at that permission code because I found a bug there
related to sys_group/task_group.
Thanks.
--
-Stephane
next prev parent reply other threads:[~2006-06-19 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 3:36 Chuck Ebbert
2006-06-19 13:36 ` Stephane Eranian [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-15 9:07 Stephane Eranian
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=20060619133626.GE25215@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®