From: "Michael Kerrisk" <mtk-lkml@gmx.net>
To: torvalds@osdl.org, akpm@osdl.org
Cc: michael.kerrisk@gmx.net, linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.10-rc2] RLIMIT_MEMLOCK accounting of shmctl() SHM_LOCK is broken
Date: Tue, 23 Nov 2004 17:36:57 +0100 (MET) [thread overview]
Message-ID: <5143.1101227817@www28.gmx.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 2480 bytes --]
Linus, Andrew,
The accounting of shmctl() SHM_LOCK memory locks against the
user structure is broken. The problem is that the check
of the size of the to-be-locked region is based on
the size of the segment as specified when it was created
by shmget() (this size is *not* rounded up to a page
boundary). This size is then rounded down (>> PAGE_SHIFT)
to PAGE_SIZE during the check in
mm/mlock.c::user_shm_lock().
The consequence is that one can lock an unlimited
number of System V shared memory segments as long as they
are each less than PAGE_SIZE bytes.
The program below can be used to demonstrate the problem.
For example, running it with the following command line:
$ ./shm_lock_many 2000 1000
creates and locks 1000 segments of 2000 bytes each,
even while RLIMIT_MEMLOCK is set to the default of 32kiB.
The simple patch at the end of this message is my
attempt at a fix (it removes the problem when I test),
but maybe there is something better.
Cheers,
Michael
=====================
/* shm_lock_many.c */
#include <sys/types.h>
#include <sys/ipc.h>
#include <sys/shm.h>
#include <sys/stat.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <string.h>
#define errExit(msg) { perror(msg); exit(EXIT_FAILURE); }
int
main(int argc, char *argv[])
{
int shmid, segSize, numSegs, j;
if (argc < 3 || strcmp(argv[1], "--help") == 0) {
fprintf(stderr, "Usage: %s segment-size num-segments\n", argv[0]);
exit(EXIT_FAILURE);
}
segSize = atoi(argv[1]);
numSegs = atoi(argv[2]);
for (j = 0; j < numSegs; j++) {
shmid = shmget(IPC_PRIVATE, segSize, S_IRUSR | S_IWUSR);
if (shmid == -1) errExit("shmget");
printf("%d: %d\n", j, shmid);
if (shmctl(shmid, SHM_LOCK, NULL) == -1) errExit("shmctl");
}
exit(EXIT_SUCCESS);
} /* main */
=======================
--- linux-2.6.10-rc2/mm/mlock.c 2004-11-23 16:47:38.368147856 +0100
+++ linux-2.6.10-rc2-mlf/mm/mlock.c 2004-11-23 17:06:10.853024448 +0100
@@ -211,7 +211,7 @@
int allowed = 0;
spin_lock(&shmlock_user_lock);
- locked = size >> PAGE_SHIFT;
+ locked = (size + PAGE_SIZE - 1) >> PAGE_SHIFT;
lock_limit = current->signal->rlim[RLIMIT_MEMLOCK].rlim_cur;
lock_limit >>= PAGE_SHIFT;
if (locked + user->locked_shm > lock_limit && !capable(CAP_IPC_LOCK))
--
NEU +++ DSL Komplett von GMX +++ http://www.gmx.net/de/go/dsl
GMX DSL-Netzanschluss + Tarif zum supergünstigen Komplett-Preis!
next reply other threads:[~2004-11-23 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 16:36 Michael Kerrisk [this message]
2004-11-23 17:04 ` Andrew Morton
2004-11-23 17:55 ` Michael Kerrisk
2004-11-23 18:31 ` Hugh Dickins
2004-11-24 20:14 ` Further shmctl() SHM_LOCK strangeness Michael Kerrisk
2004-11-24 21:41 ` Hugh Dickins
2004-11-25 3:17 ` Rik van Riel
2004-11-25 8:50 ` Michael Kerrisk
2004-11-25 11:40 ` Rik van Riel
2004-11-25 12:45 ` Michael Kerrisk
2004-11-25 14:42 ` Rik van Riel
2004-11-25 16:30 ` Michael Kerrisk
2004-11-25 8:45 ` Michael Kerrisk
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=5143.1101227817@www28.gmx.net \
--to=mtk-lkml@gmx.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®