From: Adrian Cox <adrian@humboldt.co.uk>
To: Giuliano Pochini <pochini@shiny.it>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: New 745x errata
Date: 14 Nov 2003 11:00:41 +0000 [thread overview]
Message-ID: <1068807642.23764.108.camel@newt> (raw)
In-Reply-To: <XFMail.20031114114053.pochini@shiny.it>
On Fri, 2003-11-14 at 10:40, Giuliano Pochini wrote:
> > 1) The BTIC doesn't work reliably: it can cause execution of corrupted
> > instructions. (This is listed in the errata for the 7450 and 7457, but
> > not for the 7455. I'll only believe that the 7455 escaped this bug if I
> > hear confirmation out of Motorola.)
>
> Did you try to ask them about it ?
Yes, but an answer to this sort of question will normally take a few
days. I thought it was worth raising the issue on the mailing list now.
> > 2) dcbt to protected addresses can cause spurious bus cycles. This could
> > potentially be exploited from userspace to lock up hardware.
>
> Hm, a 1-cycle window this is very small. Anyway, if dc* instructions are
> used inside the kernel, we could keep them disabled in userspace only.
The kernel uses the dc* instructions in copy_page, and in prefetches
everywhere. These uses should all be safe, unless any driver prefetches
an unchecked userspace pointer. The only problem is that we don't
currently switch the value of HID0 when entering and leaving userspace.
- Adrian
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-14 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 11:05 New 745x errata Adrian Cox
2003-11-14 10:40 ` Giuliano Pochini
2003-11-14 11:00 ` Adrian Cox [this message]
2003-11-14 16:24 ` Tom Rini
2003-11-17 14:57 ` Adrian Cox
2003-11-17 15:04 ` Tom Rini
2003-11-17 15:34 ` Adrian Cox
2003-11-18 8:40 ` Giuliano Pochini
2003-11-17 15:12 ` Gabriel Paubert
2003-11-17 15:37 ` Adrian Cox
2003-11-17 15:49 ` Gabriel Paubert
2003-11-17 17:05 ` Gabriel Paubert
2003-11-17 17:34 ` Jon Masters
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=1068807642.23764.108.camel@newt \
--to=adrian@humboldt.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).