linux-kernel - Re: File corruption when using kernels 2.6.18+

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]

Message-ID: <84144f020710031235r29986ceaj3260e8271eee6ddb@mail.gmail.com>
Date:	Wed, 3 Oct 2007 22:35:24 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:	"Neil Romig" <neil@...ig.demon.co.uk>,
	linux-kernel@...r.kernel.org, hyoshiok@...aclelinux.com,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: File corruption when using kernels 2.6.18+

Hi Linus,

On 10/3/07, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> I would bet that the reason the intel-optimized memcpy triggers this is
> that the non-temporal stores just means that you go out directly on the
> bus, and it probably just shows a weakness in the chipset or bus that
> doesn't show with the normal cacheline accesses.

But that should show up with memtest too, no?

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