[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: patch for 2.1.102 swap code

To: sct@dcs.ed.ac.uk
Subject: Re: patch for 2.1.102 swap code
From: "David S. Miller" <davem@dm.cobaltmicro.com>
Date: Mon, 25 May 1998 03:07:46 -0700
CC: whawes@star.net, sct@dcs.ed.ac.uk, linux-kernel@vger.rutgers.edu, torvalds@transmeta.com, linux-mm@kvack.org, number6@the-village.bc.nu
In-reply-to: <199805241728.SAA02816@dax.dcs.ed.ac.uk> (sct@dcs.ed.ac.uk)
References: <356478F0.FE1C378F@star.net> <199805241728.SAA02816@dax.dcs.ed.ac.uk>
Sender: owner-linux-mm@kvack.org

   Date: 	Sun, 24 May 1998 18:28:48 +0100
   From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>

   The __get_free_page() may block, however, and in a threaded
   environment this will cause the loss of user data plus a memory
   leak if two threads hit this race.  However, I don't think it's
   related to the current writable cached page problems.

The mmap semaphore is held, it cannot happen.

Later,
David S. Miller
davem@dm.cobaltmicro.com

References:
- Re: patch for 2.1.102 swap code
  - From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>
- Re: patch for 2.1.102 swap code
  - From: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>

Prev by Date: Re: patch for 2.1.102 swap code
Next by Date: Re: patch for 2.1.102 swap code
Prev by thread: Re: patch for 2.1.102 swap code
Next by thread: Re: patch for 2.1.102 swap code
Index(es):
- Date
- Thread