linux-kernel - Re: [PATCH] making /proc/<pid>/limits writable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2f11576a0807301353h2d31f021m22b34d3a67e830c@mail.gmail.com>
Date:	Thu, 31 Jul 2008 05:53:44 +0900
From:	"KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
To:	"Anders Johansson" <ajohansson@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] making /proc/<pid>/limits writable

Hi Andres,

> Attached is a patch making the limits for a process writable, so it is
> possible to change the limits of a task other than current.
>
> There are many reasons why this is desirable. The core limit is to me the most
> important. If a process hangs, because of some sort of race condition that
> happens once in a blue moon, and ulimit -c is set to 0, it might take forever
> to reproduce. It would be nice to be able to change that limit dynamically, to
> be able to get a core dump.
>
> Other limits should also be settable, but for now I've only done core size.

Hmm..
I agree to your motivation.

but I have two objection.
 - this interface is slightly ugly. end user can't lean easily.
 - you don't write any documentation nor patch description about how to use.
   So, I needed to read source code for know about how to use.
--
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/