linux-kernel - Re: Linux 3.1-rc7

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

Message-ID: <CA+55aFzrm4a_DZ0V4OQjCJYo7_7u9iTwS+2ssjqadPw1SgBLdQ@mail.gmail.com>
Date:	Wed, 28 Sep 2011 09:59:45 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arnaud Lacombe <lacombar@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.1-rc7

On Wed, Sep 28, 2011 at 9:38 AM, Arnaud Lacombe <lacombar@...il.com> wrote:
>
> At some point I did not trust the internal disk, but SMART tests
> (`short', `'long', `conveyance') passed successfully. I'd assume that
> a bad cable issue between the USB adapter and the disk would be caught
> by the UDMA_CRC_Error_Count counter (it already did), and would be
> somehow truly random. I'm not sure if USB do any kind of data checksum
> between the host and the device. I'd assume so.

I forget what the exact physical level rules are, I wouldn't really
expect all devices to necessarily even check the checksums. There's
some real crap out there.

Iirc, the common USB packet size is 512 bytes, so your corruption
pattern could match that "end of a packet" kind of rule (especially
with the header to specify where the write goes). I dunno. Hardware
problems can be a nasty nasty issue to debug.

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