All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Florian Lohoff <flo@rfc822.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-mips@linux-mips.org, debian-mips@lists.debian.org
Subject: Re: Tester with IP27/IP30 needed
Date: Tue, 05 Feb 2008 02:11:06 -0500	[thread overview]
Message-ID: <47A80C0A.4040106@gentoo.org> (raw)
In-Reply-To: <20080203062711.GA28394@paradigm.rfc822.org>

Florian Lohoff wrote:
> On Sun, Feb 03, 2008 at 03:16:48AM +0100, Ralf Baechle wrote:
>> On Sat, Feb 02, 2008 at 05:08:31PM -0500, Kumba wrote:
>>
>>> Thomas Bogendoerfer wrote:
>>>> no suprise here. As Ralf already noted cache barrier is a restricted
>>>> instruction, it will always cause a illegal instruction when used
>>>> in user space. Nevertheless it looks like all IP28 are affected
>>>> by the simple exploit. Flo built glibc 2.7 with LLSC war workaround
>>>> and this avoids triggering the hang.
>>> Ah, didn't know the 'cache' instructions was kernel-mode only.  Explains 
>>> why it survived then :)
>>>
>>> How does one enable the LLSC war workaround in glibc?
>> By modifying the code ;-)
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462112
> 
> Flo

Interesting.  Is there a reason the kernel uses an #ifdef to choose between 
'bezq' and 'bezql' that's not needed in glibc itself?  Or does glibc itself lack 
a mechanism to detect CPU types to single out this specific change?

And any idea if uClibc will need similar mods?


Thanks!,

--Kumba

-- 
Gentoo/MIPS Team Lead

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

  reply	other threads:[~2008-02-05  7:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 11:24 Tester with IP27/IP30 needed Thomas Bogendoerfer
2008-01-15 11:27 ` Florian Lohoff
2008-01-17  0:40   ` Thomas Bogendoerfer
2008-01-17  8:27     ` Florian Lohoff
2008-01-17 10:00       ` Thomas Bogendoerfer
2008-01-17 15:10       ` Ralf Baechle
2008-01-19 19:12         ` Thomas Bogendoerfer
2008-01-17 11:59     ` Ralf Baechle
2008-01-22 15:20     ` Kumba
2008-01-22 15:49       ` Ralf Baechle
2008-01-26  3:12         ` Kumba
2008-01-26 14:39           ` Thomas Bogendoerfer
2008-02-02 22:08             ` Kumba
2008-02-03  2:16               ` Ralf Baechle
2008-02-03  6:27                 ` Florian Lohoff
2008-02-05  7:11                   ` Kumba [this message]
2008-02-05 12:22                     ` Thiemo Seufer
2008-02-06  3:25                       ` Kumba
2008-02-06  8:56                         ` Florian Lohoff
2008-02-06 14:22                           ` Ralf Baechle
2008-02-08 17:23                             ` Florian Lohoff
2008-02-08 19:05                               ` Thiemo Seufer
2008-02-08 19:29                               ` Ralf Baechle
2008-02-07  5:30                           ` Kumba
2008-02-05 15:23                     ` Ralf Baechle
2008-01-23  8:47       ` peter fuerst
2008-01-15 13:11 ` Ralf Baechle
2008-01-15 13:53   ` Ralf Baechle
2008-01-15 18:18     ` Ralf Baechle
2008-01-16 16:03       ` Ralf Baechle

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=47A80C0A.4040106@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=debian-mips@lists.debian.org \
    --cc=flo@rfc822.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    /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.