From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org,
linux-mm <linux-mm@kvack.org>, David Miller <davem@davemloft.net>
Subject: Re: Recent mm changes leading to filesystem corruption?
Date: Sat, 16 Dec 2006 21:55:16 +0100 [thread overview]
Message-ID: <1166302516.10372.5.camel@twins> (raw)
In-Reply-To: <20061216155044.GA14681@deprecation.cyrius.com>
On Sat, 2006-12-16 at 16:50 +0100, Martin Michlmayr wrote:
> Debian recently applied a number of mm changes that went into 2.6.19
> to their 2.6.18 kernel for LSB 3.1 compliance (msync() had problems
> before). Since then, some filesystem corruption has been observed
> which can be traced back to these mm changes. Is anyone aware of
> problems with these patches?
As said by Hugh, no we were not.
> The patches that were applied are:
>
> - mm: tracking shared dirty pages
> - mm: balance dirty pages
> - mm: optimize the new mprotect() code a bit
> - mm: small cleanup of install_page()
> - mm: fixup do_wp_page()
> - mm: msync() cleanup
>
> With these applied to 2.6.18, the Debian installer on a slow ARM
> system fails because a program segfaults due to filesystem corruption:
> http://bugs.debian.org/401980 This problem also occurs if you only
> apply the "mm: tracking shared dirty pages" patch to 2.6.18 from the
> series of 5 patches listed above.
This made me think of a blog entry by DaveM from some time ago:
http://vger.kernel.org/~davem/cgi-bin/blog.cgi/2006/06/09
> Another problem has been reported related to libtorrent: according to
> http://bugs.debian.org/402707 someone also saw this with non-Debian
> 2.6.19 but obviously it's hard to say whether the bugs are really
> related.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394392;msg=24 shows
> some dmesg messages but again it's not 100% clear it's the same bug.
>
> Has anyone else seen problems or is aware of a fix to the patches
> listed above that I'm unaware of? It's possible the problem only
> shows up on slow systems. (The corruption is reproducible on a slow
> NSLU2 ARM system with 32 MB ram, but it doesn't happen on a faster ARM
> box with more RAM.)
What is not clear from all these reports is what architectures this is
seen on. I suspect some of them are i686, which together with the
explicit mention of ARM make it a cross platform issue.
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-12-16 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061216155044.GA14681@deprecation.cyrius.com>
2006-12-16 18:20 ` Hugh Dickins
2006-12-16 18:44 ` Martin Michlmayr
2006-12-16 19:07 ` Hugh Dickins
2006-12-16 20:55 ` Peter Zijlstra [this message]
2006-12-16 21:23 ` Martin Michlmayr
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=1166302516.10372.5.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=debian-kernel@lists.debian.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tbm@cyrius.com \
/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