[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3lkcbu3ps.fsf@maximus.localdomain>
Date: Thu, 16 Aug 2007 13:19:11 +0200
From: Krzysztof Halasa <khc@...waw.pl>
To: "Anand Jahagirdar" <anandjigar@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Fork Bombing Patch
"Anand Jahagirdar" <anandjigar@...il.com> writes:
> +++ linux-2.6.17/kernel/fork.c
> + /*
> + * following code does not allow Non Root User to cross its process
> + * limit and it alerts administrator about user Nearing the process limit.
> + */
> +
> if (atomic_read(&p->user->processes) >= p->signal->rlim[RLIMIT_NPROC].rlim_cur)
> if (!capable(CAP_SYS_ADMIN) && !capable(CAP_SYS_RESOURCE) &&
> - p->user != &root_user)
> + p->user != &root_user) {
> + if (printk_ratelimit())
> + printk(KERN_WARNING "User with uid %u is Nearing the process limit\n",p->user->uid);
> +
> goto bad_fork_free;
At least make that configurable - on some systems users are allowed
50 processes or so and I'm sure admins don't really want to know
which particular users are currently close to limits.
I don't really find the above useful. Perhaps we should warn when users
try to write to R/O files or execute root-only commands etc?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists