linux-kernel - Re: [PATCH v3 10/11] rlimits: implement prlimit64 syscall

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: <20100526073045.ea26740f.akpm@linux-foundation.org>
Date:	Wed, 26 May 2010 07:30:45 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	adobriyan@...il.com, nhorman@...driver.com, oleg@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 10/11] rlimits: implement prlimit64 syscall

On Wed, 26 May 2010 14:58:05 +0200 Jiri Slaby <jirislaby@...il.com> wrote:

> > This could all be done in userspace, couldn't it?  Write a little library
> > which clones a thread then waits for someone to send it a
> > change-your-rlimits message.  Write a little tool to send those
> > messages and voila.
> 
> Sorry, I'm not sure I understand this. Could you shed some light on what
> will run in the new thread?
> 
> A code such as:
> main()
> {
>   if (!clone())
>     exec("something");
> 
>   while (wait_for_message(&m)) {
>      setrlimit(m);
>      sleep();
>   }
> }
> won't obviously work. Could you change it so it reflects your idea or
> explain what I'm missing?

main()
{
	if (clone(...)) {
		while (wait_for_message(&m))
			setrlimit(m);
	}

	...
}
		
?
--
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/