From: "Stephen C. Tweedie" <sct@redhat.com>
To: Christoph Rohland <cr@sap.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
"Sergey E. Volkov" <sve@raiden.bancorp.ru>,
linux-kernel@vger.kernel.org
Subject: Re: VM subsystem bug in 2.4.0 ?
Date: Tue, 9 Jan 2001 15:31:19 +0000 [thread overview]
Message-ID: <20010109153119.G9321@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101081003410.3750-100000@penguin.transmeta.com> <Pine.LNX.4.21.0101081621590.21675-100000@duckman.distro.conectiva> <20010109140932.E4284@redhat.com> <qwwhf387p4s.fsf@sap.com>
In-Reply-To: <qwwhf387p4s.fsf@sap.com>; from cr@sap.com on Tue, Jan 09, 2001 at 03:53:55PM +0100
Hi,
On Tue, Jan 09, 2001 at 03:53:55PM +0100, Christoph Rohland wrote:
>
> On Tue, 9 Jan 2001, Stephen C. Tweedie wrote:
> > But again, how do you clear the bit? Locking is a per-vma property,
> > not per-page. I can mmap a file twice and mlock just one of the
> > mappings. If you get a munlock(), how are you to know how many
> > other locked mappings still exist?
>
> It's worse: The issue we are talking about is SYSV IPC_LOCK.
The issue is locked VA pages. SysV is just one of the ways in which
it can happen: the solution has got to address both that and
mlock()/mlockall().
> This is a
> per segment thing. A user can (un)lock a segment at any time. But we
> do not have the references to the vmas attached to the segemnts
Why not? Won't the address space mmap* lists give you this?
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-09 15:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 8:46 VM subsystem bug in 2.4.0 ? Sergey E. Volkov
2001-01-08 18:00 ` Rik van Riel
2001-01-08 18:10 ` Linus Torvalds
2001-01-08 18:30 ` Rik van Riel
2001-01-09 7:52 ` Christoph Rohland
2001-01-09 14:09 ` Stephen C. Tweedie
2001-01-09 14:53 ` Christoph Rohland
2001-01-09 15:31 ` Stephen C. Tweedie [this message]
2001-01-09 15:45 ` Christoph Rohland
2001-01-09 16:05 ` Stephen C. Tweedie
2001-01-09 16:17 ` Christoph Rohland
2001-01-09 18:37 ` Linus Torvalds
2001-01-09 16:45 ` Daniel Phillips
2001-01-17 8:33 ` Rik van Riel
2001-01-18 8:23 ` Christoph Rohland
2001-01-25 22:47 ` Daniel Phillips
2001-01-09 18:36 ` Linus Torvalds
2001-01-09 18:23 ` Linus Torvalds
2001-01-09 22:20 ` Christoph Rohland
2001-01-09 22:59 ` Linus Torvalds
2001-01-10 7:33 ` Christoph Rohland
2001-01-10 15:50 ` Tim Wright
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=20010109153119.G9321@redhat.com \
--to=sct@redhat.com \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=sve@raiden.bancorp.ru \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.