From: Rik van Riel <riel@conectiva.com.br>
To: Andrea Arcangeli <andrea@suse.de>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Ben LaHaise <bcrl@redhat.com>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [patch] shrink_mmap() 2.3.99-pre6-3 (take 3)
Date: Wed, 19 Apr 2000 19:58:29 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0004191952110.12458-100000@duckman.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.21.0004200035050.4117-100000@alpha.random>
On Thu, 20 Apr 2000, Andrea Arcangeli wrote:
> On Wed, 19 Apr 2000, Rik van Riel wrote:
>
> >will be needed. It also doesn't eliminate a possible race
> >condition (afaik Ben is working on that one) in shrink_mmap().
>
> Which shrink_mmap race condition?
Oh, you're right. I was worried about what would happen if we
looped back in the while() loop without the lock held, but now
I see that we grab the pagemap_lru_lock in unlock_continue...
I guess shrink_mmap() needs some comments. ;)
> >The patch does the following:
> >- remove possible race condition from truncate_inode_pages()
>
> Which truncate_inode_pages race condition? Please provide a
> stack trace, it shouldn't take too time for you if you have the
> race condition in mind.
Stephen has already answered this question a number of
emails ago.
regards,
Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.
Wanna talk about the kernel? irc.openprojects.net / #kernelnewbies
http://www.conectiva.com/ http://www.surriel.com/
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-04-19 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-19 22:09 Rik van Riel
2000-04-19 22:38 ` Andrea Arcangeli
2000-04-19 22:58 ` Rik van Riel [this message]
2000-04-19 23:12 ` Andrea Arcangeli
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.4.21.0004191952110.12458-100000@duckman.conectiva \
--to=riel@conectiva.com.br \
--cc=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@nl.linux.org \
--cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox