From: Jiri Slaby <jslaby@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT] writable_limits for 2.6.36
Date: Sat, 07 Aug 2010 14:15:12 +0200 [thread overview]
Message-ID: <4C5D4E50.5050105@suse.cz> (raw)
Hello,
please consider the following repository for 2.6.36. It introduces a new
syscall for arch independent resource limits handling. It also adds a
support for runtime limits changing. This feature is needed mostly by
daemons servicing databases and similar service where limits are needed
to be changed without services being restarted on production systems.
The following changes since commit 2f7989efd4398d92b8adffce2e07dd043a0895fe:
Merge master.kernel.org:/home/rmk/linux-2.6-arm (2010-07-14 17:28:13
-0700)
are available in the git repository at:
git://decibel.fi.muni.cz/~xslaby/linux writable_limits
Jiri Slaby (10):
rlimits: security, add task_struct to setrlimit
rlimits: add task_struct to update_rlimit_cpu
rlimits: split sys_setrlimit
rlimits: allow setrlimit to non-current tasks
rlimits: do security check under task_lock
rlimits: add rlimit64 structure
rlimits: redo do_setrlimit to more generic do_prlimit
rlimits: switch more rlimit syscalls to do_prlimit
rlimits: implement prlimit64 syscall
unistd: add __NR_prlimit64 syscall numbers
Oleg Nesterov (2):
rlimits: make sure ->rlim_max never grows in sys_setrlimit
rlimits: selinux, do rlimits changes under task_lock
arch/x86/ia32/ia32entry.S | 1 +
arch/x86/include/asm/unistd_32.h | 3 +-
arch/x86/include/asm/unistd_64.h | 2 +
arch/x86/kernel/syscall_table_32.S | 1 +
include/asm-generic/unistd.h | 4 +-
include/linux/posix-timers.h | 2 +-
include/linux/resource.h | 9 ++
include/linux/security.h | 9 +-
include/linux/syscalls.h | 4 +
kernel/compat.c | 17 +---
kernel/posix-cpu-timers.c | 8 +-
kernel/sys.c | 202
++++++++++++++++++++++++++++--------
security/capability.c | 3 +-
security/security.c | 5 +-
security/selinux/hooks.c | 12 ++-
15 files changed, 207 insertions(+), 75 deletions(-)
thanks,
--
js
suse labs
next reply other threads:[~2010-08-07 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 12:15 Jiri Slaby [this message]
2010-08-10 16:01 ` [GIT] writable_limits for 2.6.36 Linus Torvalds
2010-08-10 16:21 ` Chris Metcalf
2010-08-10 16:43 ` Jiri Slaby
2010-08-10 18:50 ` Arnd Bergmann
2010-08-10 19:12 ` Linus Torvalds
2010-08-10 19:43 ` Chris Metcalf
2010-08-10 21:44 ` Jiri Slaby
2010-08-11 2:39 ` Arnd Bergmann
2010-08-10 16:24 ` Linus Torvalds
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=4C5D4E50.5050105@suse.cz \
--to=jslaby@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.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