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

Re: [patch] take 2 Re: PG_swap_entry bug in recent kernels

To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Subject: Re: [patch] take 2 Re: PG_swap_entry bug in recent kernels
From: Andrea Arcangeli <andrea@suse.de>
Date: Sun, 9 Apr 2000 01:58:52 +0200 (CEST)
cc: Ben LaHaise <bcrl@redhat.com>, riel@nl.linux.org, Linus Torvalds <torvalds@transmeta.com>, linux-mm@kvack.org
In-Reply-To: <200004082318.QAA60782@google.engr.sgi.com>
Sender: owner-linux-mm@kvack.org

On Sat, 8 Apr 2000, Kanoj Sarcar wrote:

>[..] if you were to send out a list of
>the specific races it is fixing. (Something like my above race example).

Hug, writing the traces for all the possible races would take me really
lots of time. Writing traces is fine for showing _the_ buggy path, but it
doesn't seems the right approch for explaning and understanding how some
new code works. The comment should explain how the new locking works
against swapoff. I'd very much prefer specific questions and
comments.

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.eu.org/Linux-MM/

References:
- Re: [patch] take 2 Re: PG_swap_entry bug in recent kernels
  - From: kanoj@google.engr.sgi.com (Kanoj Sarcar)

Prev by Date: Re: zap_page_range(): TLB flush race
Next by Date: Re: zap_page_range(): TLB flush race
Prev by thread: Re: [patch] take 2 Re: PG_swap_entry bug in recent kernels
Next by thread: Re: [patch] take 2 Re: PG_swap_entry bug in recent kernels
Index(es):
- Date
- Thread