mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Gelmini <gelma@gelma.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	a.bonometti@gmail.com
Subject: Re: VM: Fix nasty and subtle race in shared mmap'ed page writeback
Date: Thu, 4 Jan 2007 14:08:23 +0100	[thread overview]
Message-ID: <20070104130823.GB28470@gelma.net> (raw)
In-Reply-To: <20070103221220.c4589831.akpm@osdl.org>

On Wed, Jan 03, 2007 at 10:12:20PM -0800, Andrew Morton wrote:
> > Anyway that leaves us with the question of why Andrea's database is getting
> > corrupted. Hopefully he can give us a minimal test-case.
> 
> It'd odd that stories of pre-2.6.19 BerkeleyDB corruption are now coming
> out of the woodwork.  It's the first I've ever heard of them.

of course, because nobody had never thought it could be a kernel bug.
since first release of klibido we had db corruption. so Bauno, main
author/programmer, introduced various check in it. so we had found db
corruption. he had talked with sleepycat (it happens long before Oracle
buys them), they were very kind, but in the meanwhile lot of code was
changed, so he had decided to wait for other tests.
anyway, in the klibido mailing list people started to complain about
corruption db. we spended a lot of time trying to find clues. anyway, to
make this part very short, after months we got clear that with Red
Hat/Suse kernel we got no crash, and with
vanilla/Debian/Ubuntu/Slackware we can reproduce it with simple action.
so, we started checking klibido code, g++ versions, qt/kde versions, and
so on. but nothing changed.
well, all this story could mean nothing, but then I said "let's look at
other projects using bdb", and I subscribed to different mailing lists.
you can change klibido with postgrey/bogofilter, and you've same story.
if you have time to look at their mailing list archive, you'll see
people complain about db corruption, people telling them "it happens",
and, usually, switching to sqlite.
nobody wrote/write to kernel mailing list because nobody thought/think
it could be a kernel bug.

anyway, the important thing is that I can give you an image of my debian
machine where you can have a lot/not at all corruption just switching
bitween debian kernel (linux-image-2.6.18-3-686) and vanilla
2.6.20-rc2-git1.

by the way, klibido works also under BSD, and we have no bug report
about db corruption (I know, we dunno how many user, which DB size, and
so on).

I repeat, all these things are not so important because klibido, but
because in common with other projects.

I put Bauno, klibido author, in Cc (it also speak english better thank
me...)

thanks a lot for your time,
gelma 

  parent reply	other threads:[~2007-01-04 13:08 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 ` Andrea Gelmini
2006-12-31  3:55   ` Nick Piggin
2006-12-31 13:50     ` Andrea Gelmini
2007-01-04  3:57       ` Nick Piggin
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 [this message]
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=20070104130823.GB28470@gelma.net \
    --to=gelma@gelma.net \
    --cc=a.bonometti@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --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

all inboxes | Powered by JetHome®