From: Al Boldi <a1426z@gawab.com>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] threads_max: Simple lockout prevention patch
Date: Mon, 14 Nov 2005 23:27:18 +0300 [thread overview]
Message-ID: <200511142327.18510.a1426z@gawab.com> (raw)
Simple attempt to provide a backdoor in a process lockout situation.
echo $$ > /proc/sys/kernel/su-pid allows pid to exceed the threads_max limit.
Signed-off-by: Al Boldi <a1426z@gawab.com>
---
(patch against 2.6.14)
--- kernel/fork.c.orig 2005-11-14 20:55:33.000000000 +0300
+++ kernel/fork.c 2005-11-14 20:58:25.000000000 +0300
@@ -57,6 +57,7 @@
int nr_threads; /* The idle threads do not count.. */
int max_threads; /* tunable limit on nr_threads */
+int su_pid; /* BackDoor pid to exceed limit on nr_threads
*/
DEFINE_PER_CPU(unsigned long, process_counts) = 0;
@@ -926,6 +927,7 @@
* to stop root fork bombs.
*/
if (nr_threads >= max_threads)
+ if (p->pid != su_pid)
goto bad_fork_cleanup_count;
if (!try_module_get(p->thread_info->exec_domain->module))
--- kernel/sysctl.c.orig 2005-11-14 20:58:45.000000000 +0300
+++ kernel/sysctl.c 2005-11-14 21:01:20.000000000 +0300
@@ -57,6 +57,7 @@
extern int sysctl_overcommit_memory;
extern int sysctl_overcommit_ratio;
extern int max_threads;
+extern int su_pid;
extern int sysrq_enabled;
extern int core_uses_pid;
extern int suid_dumpable;
@@ -509,6 +510,14 @@
.proc_handler = &proc_dointvec,
},
{
+ .ctl_name = KERN_SU_PID,
+ .procname = "su-pid",
+ .data = &su_pid,
+ .maxlen = sizeof(int),
+ .mode = 0644,
+ .proc_handler = &proc_dointvec,
+ },
+ {
.ctl_name = KERN_RANDOM,
.procname = "random",
.mode = 0555,
--- include/linux/sysctl.h.orig 2005-11-14 20:54:55.000000000 +0300
+++ include/linux/sysctl.h 2005-11-14 20:55:15.000000000 +0300
@@ -146,6 +146,7 @@
KERN_RANDOMIZE=68, /* int: randomize virtual address space */
KERN_SETUID_DUMPABLE=69, /* int: behaviour of dumps for setuid core
*/
KERN_SPIN_RETRY=70, /* int: number of spinlock retries */
+ KERN_SU_PID=71, /* int: BackDoor pid to exceed Maximum nr of threads
in the system */
};
next reply other threads:[~2005-11-14 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 20:27 Al Boldi [this message]
2006-01-30 13:21 ` Al Boldi
2006-04-24 4:56 ` Al Boldi
2006-04-24 5:11 ` Andrew Morton
2006-04-24 11:12 ` Al Boldi
2006-04-24 11:22 ` Pekka Enberg
2006-04-24 13:53 ` Al Boldi
2006-04-24 14:11 ` Pekka Enberg
2006-04-24 14:46 ` Al Boldi
2006-04-24 16:32 ` Pekka Enberg
2006-04-24 11:24 ` Nick Piggin
2006-04-24 13:37 ` Al Boldi
2006-04-25 7:23 ` Nick Piggin
2006-04-25 10:44 ` Al Boldi
2006-04-28 16:58 ` Al Boldi
2006-04-24 7:10 ` Theodore Ts'o
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=200511142327.18510.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome