Bug#247300: libc6: malloc() never fails on 2.4 kernels, making processes crash
On Thu, May 06, 2004 at 10:34:05PM +0200, Vincent Lefevre wrote:
> On 2004-05-06 12:25:19 -0400, Daniel Jacobowitz wrote:
> > Overcommit does not work properly in 2.4, though. GOTO-san is right -
> > from your description you want strict overcommit, i.e. the value of 2
> > for this flag. Some of the 2.4-ac kernels had this. So does 2.6.
>
> This is strange, because 3 different users[*] told me that the 2.4
> kernel was OK for me. And according to the 2.4 vm.txt documentation,
> setting the overcommit_memory flag to 0 in the 2.4 kernel should be
> sufficient (otherwise the documentation is plainly wrong).
>
> [*] Msgid <Pine.LNX.4.33.0403151627540.2144-100000@patchwork.seclogd.org>
> and <pxbfzc8kgos.fsf@news.bourguet.org> for the first two, and in a
> private forum for the last one (and this one said that this was working
> in the past with an official 2.4 kernel, i.e. non-patched).
This is strange, because many people at MV have told me the opposite.
At least one of the people who suggested it to you (2nd message-ID
above) was using a patched distro kernel from one of the Enterprise
distributions. They've all done local work in this area during the 2.4
timeframe.
The documentation in the 2.4 kernel is, indeed, wrong IIRC.
BTW, from 2.6:
In mode 2 the MAP_NORESERVE flag is ignored.
--
Daniel Jacobowitz
Reply to: