From: "Mr. Berkley Shands" <bshands@exegy.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.14-rc5 mlock/munlock bug
Date: Fri, 21 Oct 2005 13:51:10 -0500 [thread overview]
Message-ID: <4359389E.6030406@exegy.com> (raw)
I've noticed that between 2.6.14-rc2 and 2.6.14-rc5 mlock() and
mlunlock() have broken.
a call to mlock() to lock pages is granted, and the pages are locked,
but never
unlocked, even when munlock() is manually called or at process rundown.
No problems under 2.6.13 or up to 2.6.14-rc2. But sometime after -rc2 it
goes BANG
and the machine gets very unhappy. If you look at "swapon -s" you see
more and more swap
space is used until there is no physical memory left, then things really
get unhappy.
berkley
next reply other threads:[~2005-10-21 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 18:51 Mr. Berkley Shands [this message]
2005-10-25 21:48 ` 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=4359389E.6030406@exegy.com \
--to=bshands@exegy.com \
--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
Powered by JetHome