From: Andrew Morton <akpm@osdl.org>
To: "Michael Kerrisk" <mtk-lkml@gmx.net>
Cc: torvalds@osdl.org, michael.kerrisk@gmx.net,
linux-kernel@vger.kernel.org,
Manfred Spraul <manfred@colorfullife.com>,
Hugh Dickins <hugh@veritas.com>
Subject: Re: [PATCH 2.6.10-rc2] RLIMIT_MEMLOCK accounting of shmctl() SHM_LOCK is broken
Date: Tue, 23 Nov 2004 09:04:49 -0800 [thread overview]
Message-ID: <20041123090449.1672494f.akpm@osdl.org> (raw)
In-Reply-To: <5143.1101227817@www28.gmx.net>
"Michael Kerrisk" <mtk-lkml@gmx.net> wrote:
>
> 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().
True. We should make the same change to user_shm_unlock(), and we may as
well tweak the excessive spinlock coverage in there too.
--- 25/mm/mlock.c~rlimit_memlock-accounting-of-shmctl-shm_lock-is-broken 2004-11-23 08:58:13.299089928 -0800
+++ 25-akpm/mm/mlock.c 2004-11-23 09:01:31.500958664 -0800
@@ -211,10 +211,10 @@ int user_shm_lock(size_t size, struct us
unsigned long lock_limit, locked;
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;
+ spin_lock(&shmlock_user_lock);
if (locked + user->locked_shm > lock_limit && !capable(CAP_IPC_LOCK))
goto out;
get_uid(user);
@@ -228,7 +228,7 @@ out:
void user_shm_unlock(size_t size, struct user_struct *user)
{
spin_lock(&shmlock_user_lock);
- user->locked_shm -= (size >> PAGE_SHIFT);
+ user->locked_shm -= (size + PAGE_SIZE - 1) >> PAGE_SHIFT);
spin_unlock(&shmlock_user_lock);
free_uid(user);
}
_
and then ask Hugh and Manfred to double-check.
Looking at the callers, we do:
user_shm_lock(inode->i_size, ...);
then, later:
user_shm_unlock(inode->i_size, ...);
which does make one wonder "what happens if the file got larger while it
was locked"?
next prev parent reply other threads:[~2004-11-23 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 16:36 Michael Kerrisk
2004-11-23 17:04 ` Andrew Morton [this message]
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=20041123090449.1672494f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-lkml@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®