From: Andrea Arcangeli <andrea@suse.de>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: linux-mm@kvack.org
Subject: Re: Use of mmap_sem in map_user_kiobuf
Date: Fri, 6 Jul 2001 18:56:23 +0200 [thread overview]
Message-ID: <20010706185623.C2425@athlon.random> (raw)
In-Reply-To: <3B4597FE.7070901@humboldt.co.uk>; from adrian@humboldt.co.uk on Fri, Jul 06, 2001 at 11:50:38AM +0100
On Fri, Jul 06, 2001 at 11:50:38AM +0100, Adrian Cox wrote:
> Does map_user_kiobuf really need to get a write lock on the mmap_sem?
> From examination of the code, all it can do is expand_stack(), fault in
> pages, and increment the count on a page.
>
> Is there anything I've missed? Would it be safe to use down_read(),
> up_read() instead?
yes, it should be ok.
Andrea
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2001-07-06 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 10:50 Adrian Cox
2001-07-06 16:56 ` Andrea Arcangeli [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=20010706185623.C2425@athlon.random \
--to=andrea@suse.de \
--cc=adrian@humboldt.co.uk \
--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