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]

Date:	Tue, 02 Oct 2007 22:05:19 +0100
From:	Neil Romig <neil@...ig.demon.co.uk>
To:	Pekka Enberg <penberg@...helsinki.fi>
CC:	linux-kernel@...r.kernel.org, hyoshiok@...aclelinux.com
Subject: Re: File corruption when using kernels 2.6.18+

Pekka Enberg wrote:
> Hi Neil,
> 
> On 9/30/07, Neil Romig <neil@...ig.demon.co.uk> wrote:
>> I would suspect a memory problem but memtest86+ gives no errors despite numerous
>> passes, and I get no errors in older kernels. Does anyone have any idea what changed in
>> 2.6.18 to cause such an error?
> 
> I don't but you can try to isolate the changeset introducing the
> corruption with git-bisect:
> 
> http://kernel.org/pub/software/scm/git/docs/v1.3.3/howto/isolate-bugs-with-bisect.txt
> 
> So, in your case, you do:
> 
> <clone Linux mainline git repository>
> # git bisect start
> # git bisect bad v2.6.18
> # git bisect good v2.6.17
> 
> then
> 
> <recompile and test>
> <git bisect [good|bad] depending on results>
> <repeat until you've narrowed down the changeset>
> 
> Also, please remember to send your .config when reporting bugs as
> described in REPORTING-BUGS.
> 
>                                          Pekka
> 
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!

My kernel .config is attached, along with lspci output.

Neil

View attachment "config" of type "text/plain" (32741 bytes)

View attachment "lspci" of type "text/plain" (4404 bytes)