From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Neil Booth <NeilB@earthling.net>
Cc: linux-mm@kvack.org
Subject: Re: vmalloc.c question
Date: Fri, 19 Feb 1999 14:43:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.990219144204.970A-100000@as200.spellcast.com> (raw)
In-Reply-To: <36CD3BCE.9D2AE90E@earthling.net>
On Fri, 19 Feb 1999, Neil Booth wrote:
> I have a simple question about vmalloc.c. I'm probably missing something
> obvious, but it appears to me that the list "vmlist" of the kernel's
> virtual memory areas is not protected by any kind of locking mechanism,
> and thus subject to races. (e.g. two CPUs trying to insert a new virtual
> memory block in the same place at the same time in get_vm_area).
That's probably because it assumes the caller holds the global kernel
lock (which is okay -- vmalloc can't be called from bottom half or irq
context safely anyways).
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-02-19 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-19 10:24 Neil Booth
1999-02-19 18:11 ` Kanoj Sarcar
1999-02-19 19:43 ` Benjamin C.R. LaHaise [this message]
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=Pine.LNX.3.95.990219144204.970A-100000@as200.spellcast.com \
--to=blah@kvack.org \
--cc=NeilB@earthling.net \
--cc=linux-mm@kvack.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