From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrea Gelmini <gelma@gelma.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: VM: Fix nasty and subtle race in shared mmap'ed page writeback
Date: Thu, 04 Jan 2007 14:57:24 +1100 [thread overview]
Message-ID: <459C7B24.8080008@yahoo.com.au> (raw)
In-Reply-To: <20061231135031.GC23445@gelma.net>
Andrea Gelmini wrote:
> On Sun, Dec 31, 2006 at 02:55:58PM +1100, Nick Piggin wrote:
>
>>This bug was only introduced in 2.6.19, due to a change that caused pte
>
> no, Linus said that with 2.6.19 it's easier to trigger this bug...
Yhat's when the bug was introduced -- 2.6.19. 2.6.18 does not have
this bug, so it cannot be years old.
>>So if your corruption is years old, then it must be something else.
>>Maybe it is hidden by a timing change, or BDB isn't using msync properly.
>
> I can give you a complete image where just changing kernel (everything
> is same, of course) corruptions goes away.
> we spent a lot, I mean a *lot*, of time looking for our code mistake,
> and so on.
> I don't want to seem rude, but I am sure that Berkeley DB corruption we
> have seen (not just Klibido, but I also think about postgrey, and so on)
> depends on this bug.
> I repeat, if you have time/interest I can give you a complete machine
> to see the problem.
You're not being rude, but I just wanted to point out that this patch
(nor the dirty page accounting also in 2.6.19) doesn't fix anything
that was in 2.6.18, AFAIKS.
I wouldn't discount a kernel bug, but it will be hard to track down
unless you can find an earlier kernel that did not cause the corruptions
and/or provide source for a minimal test case to reproduce.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2007-01-04 3:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612291859.kBTIx2kq031961@hera.kernel.org>
2006-12-29 22:43 ` VM: Fix nasty and subtle race in shared mmap'ed page writeback Andrea Gelmini
2006-12-31 3:55 ` Nick Piggin
2006-12-31 13:50 ` Andrea Gelmini
2007-01-04 3:57 ` Nick Piggin [this message]
2007-01-04 4:44 ` Linus Torvalds
2007-01-04 5:07 ` Nick Piggin
2007-01-04 13:17 ` Andrea Gelmini
2007-01-04 5:41 ` Andrew Morton
2007-01-04 6:03 ` Nick Piggin
2007-01-04 6:12 ` Andrew Morton
2007-01-04 6:56 ` David Miller
2007-01-04 7:06 ` Andrew Morton
2007-01-04 7:16 ` Nick Piggin
2007-01-04 13:25 ` Hugh Dickins
2007-01-08 7:46 ` dean gaudet
2007-01-04 13:08 ` Andrea Gelmini
2007-01-04 13:16 ` Andrea Gelmini
2007-01-05 5:36 ` Nick Piggin
2007-01-10 13:54 ` Andrea Gelmini
[not found] ` <1168507298.26496.18.camel@twins>
[not found] ` <20070112003955.GH4553@gelma.net>
[not found] ` <1169457039.2639.17.camel@taijtu>
2007-01-29 14:08 ` Andrea Gelmini
2007-01-29 14:11 ` Peter Zijlstra
2007-01-29 15:12 ` Andrea Arcangeli
2007-01-05 19:12 ` Christoph Lameter
2007-01-05 19:33 ` Linus Torvalds
2007-01-05 20:02 ` Christoph Lameter
2007-01-05 21:34 ` Linus Torvalds
2007-01-04 13:19 ` Andrea Gelmini
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=459C7B24.8080008@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=gelma@gelma.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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