From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: message queue limits
Date: Thu, 15 Apr 2004 11:53:50 -0300 [thread overview]
Message-ID: <20040415145350.GF2085@logos.cnet> (raw)
In-Reply-To: <407A2DAC.3080802@redhat.com>
On Sun, Apr 11, 2004 at 10:48:28PM -0700, Ulrich Drepper wrote:
> Something has to change in the way message queues are created.
> Currently it is possible for an unprivileged user to exhaust all mq
> slots so that only root can create a few more. Any other unprivileged
> user has no change to create anything.
>
> I think it is necessary to create a per-user limit instead of a
> system-wide limit.
Actually, there is no infrastructure to account for per-UID limits right now AFAICS
(please someone correct me) at ALL. We need to account and limit for per-user
- pending signals
- message queues
And all other current limits which are per "struct task".
There is CKRM available, but I suppose its not easily mergeable and not
finished yet.
There was an effort to create simple per-user limits infrastructure called
"userbeans" at some point in 2.3.x development. Maybe it needs to be
resurrected?
This is bad.
next prev parent reply other threads:[~2004-04-15 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 5:48 Ulrich Drepper
2004-04-13 20:16 ` Bill Davidsen
2004-04-15 14:53 ` Marcelo Tosatti [this message]
2004-04-15 19:24 ` Andrew Morton
2004-04-15 19:54 ` Marcelo Tosatti
2004-04-15 21:46 ` Marcelo Tosatti
2004-04-15 22:54 ` Andrew Morton
2004-04-16 0:10 ` Marcelo Tosatti
2004-04-16 1:48 ` Andrew Morton
2004-04-16 13:13 ` Marcelo Tosatti
[not found] ` <20040415141846.GE2085@logos.cnet>
[not found] ` <407EB08D.4010607@colorfullife.com>
2004-04-16 14:06 ` Marcelo Tosatti
2004-04-16 21:35 ` Andrew Morton
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=20040415145350.GF2085@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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
Powered by JetHome