|
From: Igmar P. <mai...@jd...> - 2004-10-10 17:17:34
|
> > The limit actually get's set, but is never raised. This triggers grsec, > > which rightfully complains that later allocations in the data segment > > exceed the existing limits. > > When you that it is never raised, what do you mean? It isn't supposed > to be raised in the valgrinded process - that is the whole point. It > should be restored on exec however. Is that what you are saying isn't > happening? I was confused by the manual page of brk(), since that indicates brk() returning -1 is things fail. Looking at the kernel code, brk() failing just returns the current data segment border. I'll simply patch grsec to make it shut up, since it's hardly of relevance on this devel machine. > Equally, which later alloctions in the data segment are you talking > about? The whole point is to prevent any allocations in the data > segment and force the use of mmap instead. Clear now. I'll fix up grsec in this case :) Igmar |