[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0612190847270.3479@woody.osdl.org>
Date: Tue, 19 Dec 2006 08:51:16 -0800 (PST)
From: Linus Torvalds <torvalds@...l.org>
To: Nick Piggin <nickpiggin@...oo.com.au>
cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andrew Morton <akpm@...l.org>, andrei.popa@...eo.ro,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hugh Dickins <hugh@...itas.com>,
Florian Weimer <fw@...eb.enyo.de>,
Marc Haber <mh+linux-kernel@...schlus.de>,
Martin Michlmayr <tbm@...ius.com>
Subject: Re: 2.6.19 file content corruption on ext3
On Tue, 19 Dec 2006, Nick Piggin wrote:
>
> Counterexample? Well AFAIKS, the clearing of PG_dirty in ttfb() in
> response to finding all buffers clean is perfectly valid. What makes
> you think otherwise?
If the page really is clean, then why the heck cant' we just clean the
page table bits too?
Either it's clean or it isn't. If all the buffers being clean means that
the page is clean, then it's clean. WE SHOULD NOT THINK THAT PTE'S ARE ANY
DIFFERENT.
I really don't see your point. Is it clean? If it is, then clear the damn
dirty bits from the page tables too. Don't go pussyfooting around the
issue and confuse yourself and everybody but me by saying "but if it's
dirty in the page tables, it's magically dirty". NO.
It really is that simple. Is it clean or not?
If it's clean, you can remove ALL the dirty bits. Not just some.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists