public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Gelmini <gelma@gelma.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: VM: Fix nasty and subtle race in shared mmap'ed page writeback
Date: Fri, 29 Dec 2006 23:43:09 +0100	[thread overview]
Message-ID: <20061229224309.GA23445@gelma.net> (raw)
In-Reply-To: <200612291859.kBTIx2kq031961@hera.kernel.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1049 bytes --]

On Fri, Dec 29, 2006 at 06:59:02PM +0000, Linux Kernel Mailing List wrote:
> Gitweb:     http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7658cc289288b8ae7dd2c2224549a048431222b3
> Commit:     7658cc289288b8ae7dd2c2224549a048431222b3
> Parent:     3bf8ba38f38d3647368e4edcf7d019f9f8d9184a
> Author:     Linus Torvalds <torvalds@macmini.osdl.org>
> AuthorDate: Fri Dec 29 10:00:58 2006 -0800
> Committer:  Linus Torvalds <torvalds@macmini.osdl.org>
> CommitDate: Fri Dec 29 10:00:58 2006 -0800
> 
>     VM: Fix nasty and subtle race in shared mmap'ed page writeback

With 2.6.20-rc2-git1, which contain this patch, I have no more Berkeley
DB corruption with Klibido.¹
I'm afraid a lot of software project switched to Sqlite,² from BDB,³
because the bug this patch fix (ie. http://bogofilter.sourceforge.net/).
I've also thought, since years, it was an userland problem.

Ciao,
gelma

-------------------
¹ http://klibido.sourceforge.net/
² http://www.sqlite.org/
³ http://www.oracle.com/database/berkeley-db/index.html

       reply	other threads:[~2006-12-29 22:49 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 [this message]
2006-12-31  3:55   ` VM: Fix nasty and subtle race in shared mmap'ed page writeback 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
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=20061229224309.GA23445@gelma.net \
    --to=gelma@gelma.net \
    --cc=linux-kernel@vger.kernel.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