linux-kernel - [bisected] NFS corruption with 3.4

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: <201206051116.17711.linux@rainbow-software.org>
Date:	Tue, 5 Jun 2012 11:16:17 +0200
From:	Ondrej Zary <linux@...nbow-software.org>
To:	Konstantin Khlebnikov <khlebnikov@...nvz.org>
Cc:	Hugh Dickins <hughd@...gle.com>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: [bisected] NFS corruption with 3.4

Hello,
I use NFS for deploying HDD images on new machines. My machine has 2nd network 
card just for this, running DHCPD, TFTPD and kernel NFS server. The target 
machine is set to boot from LAN and boots SystemRescueCD from my machine with 
an autorun script that launches Partimage and deploys the HDD image (400 to 
900 MB compressed).

It worked fine for years, until now. With kernel 3.4, everyting 
works only for the first time after boot (and not always). Next time (next 
machine), partimage aborts almost immediately as it's probably unable to 
decompress the image file. md5sum is different on my machine vs. on the 
target (through NFS). Also SystemRescueCD boot aborts with md5 error 
sometimes. Everything works fine after rebooting back to 3.3.

Bisection found this:

0fc9d1040313047edf6a39fd4d7c7defdca97c62 is the first bad commit
commit 0fc9d1040313047edf6a39fd4d7c7defdca97c62
Author: Konstantin Khlebnikov <khlebnikov@...nvz.org>
Date:   Wed Mar 28 14:42:54 2012 -0700

    radix-tree: use iterators in find_get_pages* functions

Reverting this commit in 3.4 fixes the problem.

-- 
Ondrej Zary
--
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/