linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Romeyke <art1@it-netservice.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: kernel 2.5:  mlock broken?
Date: Fri, 8 Aug 2003 23:32:13 +0200	[thread overview]
Message-ID: <20030808233213.4ffb2c84.art1@it-netservice.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

Hi folks,

By testing 2.6.0-test2, I detected that the glibc-function mlock(),
provided by /sys/mlock.h seems to be a deadlock in some cases on 2.5

If you want to lock more memory than physical RAM could be freed, the
mlock() does not return with an errorcode as under 2.4.21 does.
The system hangs around. This problem was catched under x86 and s390
architecture by using Debian distribution (woody and unstable) and
others  with the well known memtest program written by Charles Cazabon
from   http://www.qcc.ca/~charlesc/software/memtester/ (ver. 2.93.1).

IMHO the problem is effected in kernel  mm/mlock.c, ev. in do_mlock(),
because glibc was not changed between different kernelversions. The
glibc version was 2.3.1-17

Hope it helps.

Bye Andreas

PS.:If you think this report is not related to this list, please contact
me per private email.
PPS.: If you need further information, contact me too.

-- 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-08-08 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08 21:32 Andreas Romeyke [this message]
2003-08-08 21:49 ` kernel 2.5: mlock broken? Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030808233213.4ffb2c84.art1@it-netservice.de \
    --to=art1@it-netservice.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).