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: <84144f020710031148i346b393bm528fc150fedff00f@mail.gmail.com>
Date:	Wed, 3 Oct 2007 21:48:34 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Neil Romig" <neil@...ig.demon.co.uk>
Cc:	linux-kernel@...r.kernel.org, hyoshiok@...aclelinux.com,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: File corruption when using kernels 2.6.18+

Hi Neil,

On 10/3/07, Neil Romig <neil@...ig.demon.co.uk> wrote:
> > > Thanks for your help on this. I have narrowed it down to commit
> > > "c22ce143d15eb288543fe9873e1c5ac1c01b69a1 x86: cache pollution aware
> > > __copy_from_user_ll()". This fits with the errors I'm getting, so now I need
> > > to find out if I can safely ignore this patch, or does it have to be modified?
> > > This is my first Linux bug in many years of simply using it, so I'm a little
> > > nervous!

A some point in time, I wrote:
> > Just to make sure, if you disable CONFIG_X86_INTEL_USERCOPY, the
> > corruption goes away?

On 10/3/07, Neil Romig <neil@...ig.demon.co.uk> wrote:
> It took some fiddling to disable (edit arch/i386/Kconfig.cpu) but that has fixed it.
> Many thanks!
>
> Does this need to be reported as a bug? Or should the kernel config scripts be
> changed to enable this option to be easily turned off?

Looks like a bug to me. Can we have your /proc/cpuinfo too?

                              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/