From: Neil Romig <neil@romig.demon.co.uk>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, hyoshiok@miraclelinux.com
Subject: Re: File corruption when using kernels 2.6.18+
Date: Wed, 03 Oct 2007 19:42:15 +0100 [thread overview]
Message-ID: <4703E287.3070705@romig.demon.co.uk> (raw)
In-Reply-To: <84144f020710022218x147ffc74y477c0a1be3e60d66@mail.gmail.com>
Pekka Enberg wrote:
> Hi Neil,
>
> On 10/3/07, Neil Romig <neil@romig.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!
>
> Just to make sure, if you disable CONFIG_X86_INTEL_USERCOPY, the
> corruption goes away?
>
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?
Neil.
next prev parent reply other threads:[~2007-10-03 18:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 15:40 File corruption when using kernels 2.6.18+ Neil Romig
2007-09-30 16:29 ` Pekka Enberg
2007-10-02 21:05 ` Neil Romig
2007-10-03 5:18 ` Pekka Enberg
2007-10-03 18:42 ` Neil Romig [this message]
2007-10-03 18:48 ` Pekka Enberg
2007-10-03 19:22 ` Linus Torvalds
2007-10-03 19:35 ` Pekka Enberg
2007-10-03 19:54 ` Linus Torvalds
2007-10-04 1:11 ` Hiro Yoshioka
2007-10-03 20:30 ` Alan Cox
2007-10-04 18:34 ` Neil Romig
2007-10-02 22:30 ` Chuck Ebbert
[not found] <fa.VCoGTwbB+qeNlkBJ24MiuXcGSRA@ifi.uio.no>
[not found] ` <fa.R+FhT6IGmV/dDweUt/MdSeA5YbQ@ifi.uio.no>
[not found] ` <fa.7MxTIt/ik0uRFN/lMWUasYV/JyE@ifi.uio.no>
[not found] ` <fa.YJ4uCPzXT5TQElSosyz98cpuMSc@ifi.uio.no>
[not found] ` <fa.Tp9UUX9EYprQyLg0shgH1YG9DDM@ifi.uio.no>
[not found] ` <fa.PzpJEEoLXfC+eOQZjTWjdf9vdnE@ifi.uio.no>
2007-10-04 2:59 ` Robert Hancock
2007-10-04 3:39 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4703E287.3070705@romig.demon.co.uk \
--to=neil@romig.demon.co.uk \
--cc=hyoshiok@miraclelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.