linux-kernel - Recent mm changes leading to filesystem corruption?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061216155044.GA14681@deprecation.cyrius.com>
Date:	Sat, 16 Dec 2006 16:50:44 +0100
From:	Martin Michlmayr <tbm@...ius.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Hugh Dickins <hugh@...itas.com>, linux-kernel@...r.kernel.org,
	debian-kernel@...ts.debian.org
Subject: Recent mm changes leading to filesystem corruption?

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?

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.

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.)
-- 
Martin Michlmayr
http://www.cyrius.com/
-
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/