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

Re: 2.4.14 + Bug in swap_out.

To: "David S. Miller" <davem@redhat.com>
Subject: Re: 2.4.14 + Bug in swap_out.
From: ebiederm@xmission.com (Eric W. Biederman)
Date: 20 Nov 2001 23:37:03 -0700
Cc: torvalds@transmeta.com, linux-mm@kvack.org,linux-kernel@vger.kernel.org
Fake-Sender: owner-linux-mm@kvack.org
In-Reply-To: <20011120.222920.51691672.davem@redhat.com>
Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
References: <m1vgg41x3x.fsf@frodo.biederman.org><20011120.222920.51691672.davem@redhat.com>
Sender: Rik van Riel <riel@nl.linux.org>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1

"David S. Miller" <davem@redhat.com> writes:

> I do not agree with your analysis.

Neither do I now but not for your reasons :)

I looked again we are o.k. but just barely.  mmput explicitly checks
to see if it is freeing the swap_mm, and fixes if we are.  It is a
nasty interplay with the swap_mm global, but the code is correct.

My apologies for freaking out I but I couldn't imagine mmput doing
something like that.

Eric
--
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/

Follow-Ups:
- Re: 2.4.14 + Bug in swap_out.
  - From: Rik van Riel <riel@conectiva.com.br>

References:
- 2.4.14 + Bug in swap_out.
  - From: ebiederm@xmission.com (Eric W. Biederman)
- Re: 2.4.14 + Bug in swap_out.
  - From: "David S. Miller" <davem@redhat.com>

Prev by Date: Re: 2.4.14 + Bug in swap_out.
Next by Date: recursive lock-enter-deadlock
Prev by thread: Re: 2.4.14 + Bug in swap_out.
Next by thread: Re: 2.4.14 + Bug in swap_out.
Index(es):
- Date
- Thread