Re: runit running under linux 2.4 with openwall patches

[Charlie Brady <charlieb-supervision@budge.apana.org.au>]

On Thu, 20 Jan 2005, Vincent Danen wrote:

> One of the features of openwall is stack protection.  I'm getting this 
> when I try to boot into a 2.4.29 kernel with openwall hardening 
> enabled:
> 
> Security: return onto stack from 0x0804812c to 0xbffffea0 running as 
> UID 0, EUID 0, process runit:1
> Security more returns onto stack, logging disabled for a minute
> 
> I can manage to make the kernel boot, but runit isn't running and it's 
> consuming 100% cpu in my vmware test machine.
> 
> I have two ideas that may be causing the problem, and not being a 
> kernel person I don't really know for 100% which it is:
> 
> 1) the Non-executable user stack area part of owl
> 2) the enforce RLIMIT_NPROC on execve(2)
> 
> I have a feeling that it's #1 tho.

Why do you have that feeling? What gives you these two ideas? Do you see 
any actions from runit before the "return onto stack" message?

You might run "strace runit-init" in place of "runit", although I'm not 
sure what chaos that might cause.