linux-kernel - Re: torrent hash failures since 3.9.0-rc1

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Mar 2013 15:41:59 -0400
From:	Dave Jones <davej@...hat.com>
To:	Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc:	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: torrent hash failures since 3.9.0-rc1

On Mon, Mar 11, 2013 at 08:17:53PM +0100, Markus Trippelsdorf wrote:
 > On 2013.03.11 at 18:18 +0100, Markus Trippelsdorf wrote:
 > > I get hash failures on "completed" torrents since 3.9.0-rc1 (Linux 3.8
 > > seems to be fine). What happens is that the torrents apparently complete
 > > successfully. After reboot however the hash check fails and there are
 > > missing (or corrupted) chunks. I've tested this with two different
 > > clients (rtorrent and aria2c) and both are affected. So I think this
 > > might be a filesystem issue.
 > > 
 > > /dev/sda       ext4      1.4T  666G  640G  51% /var
 > > /dev/sda on /var type ext4 (rw,noatime,data=ordered)
 > > 
 > > I use ECC memory (and there is nothing in the logs).
 > 
 > To reproduce this issue just do the following:
 > 
 >  % wget http://torrents.linuxmint.com/torrents/linuxmint-12-gnome-cd-nocodecs-64bit.iso.torrent
 >  % rtorrent linuxmint-12-gnome-cd-nocodecs-64bit.iso.torrent
 >  (Wait until the torrent finishes)
 >  % sudo echo 3 > /proc/sys/vm/drop_caches
 >  (Rehash the torrent (Ctrl-R))
 >  The torrent doesn't rehash successfully and a few hunks are
 >  missing/corrupted and need to be downloaded again.

Worked fine for me on two separate machines.  Could it be a network problem
perhaps ? If something is mangling the packet before it hits the disk,
that would explain it.  What NIC do you use ?

Or maybe you could isolate it to a filesystem problem using something
like fsx ?

	Dave

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