From: Chris Wright <chrisw@osdl.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, torvalds@osdl.org, marcelo.tosatti@cyclades.com
Subject: [PATCH 0/11] rlimits for both queued signals and POSIX mqueues
Date: Tue, 11 May 2004 01:42:32 -0700 [thread overview]
Message-ID: <20040511014232.Y21045@build.pdx.osdl.net> (raw)
The following patches introduce per user rlimits for both queued
signals and POSIX message queues. The changes touch all the arches
resource.h files as well as init_task.c to get the rlimit defaults setup.
Both require caching the user_struct to avoid problems with setuid().
The signal changes makes some small changes to send_signal() to pass
along the task being signalled to get proper accounting for signals
initiated in interrupt. Patches are relative to 2.6.6-bk. Thanks to
Marcelo for getting this one going.
thanks,
-chris
next reply other threads:[~2004-05-11 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 8:42 Chris Wright [this message]
2004-05-11 8:45 ` [PATCH 1/11] add rlimit entry for controlling queued signals Chris Wright
2004-05-11 8:46 ` [PATCH 2/11] add sigpending field to user_struct Chris Wright
2004-05-11 8:48 ` [PATCH 3/11] pass task_struct in send_signal() Chris Wright
2004-05-11 8:50 ` [PATCH 4/11] add simple get_uid() helper Chris Wright
2004-05-11 8:52 ` [PATCH 5/11] enforce rlimits on queued signals Chris Wright
2004-05-11 8:53 ` [PATCH 6/11] remove unused queued_signals global accounting Chris Wright
2004-05-11 8:56 ` [PATCH 7/11] add rlimit entry for POSIX mqueue allocation Chris Wright
2004-05-11 8:58 ` [PATCH 8/11] add mq_bytes to user_struct Chris Wright
2004-05-11 9:00 ` [PATCH 9/11] add mq_attr_ok() helper Chris Wright
2004-05-11 9:02 ` [PATCH 10/11] enforce rlimits for POSIX mqueue allocation Chris Wright
2004-05-11 9:04 ` [PATCH 11/11] adjust default mqueue sizes Chris Wright
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=20040511014232.Y21045@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=torvalds@osdl.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®