From: Gabriel Paubert <paubert@iram.es>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: New 745x errata
Date: Mon, 17 Nov 2003 16:12:46 +0100 [thread overview]
Message-ID: <20031117151246.GA31680@iram.es> (raw)
In-Reply-To: <1069081074.10537.16.camel@newt>
On Mon, Nov 17, 2003 at 02:57:53PM +0000, Adrian Cox wrote:
>
> On Fri, 2003-11-14 at 16:24, Tom Rini wrote:
> > On Thu, Nov 13, 2003 at 11:05:17AM +0000, Adrian Cox 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.)
> >
> > I've done the opposite in something I've been waiting for 2.4.24-pre
> > to come out to fix. But I agree that it is odd that it's not listed
> > on the 7455.
>
> Still no word back from Motorola on the 7455. I think your patch
> should go in.
>
> Any opinion on the dcbt issue? It looks like it could provide a way
> for a malicious userspace application to crash the machine, though it
> needs a combination of:
> 1) good timing
> 2) a peripheral that would be confused by an extra read cycle
Well, only privileged applications should have access to
peripherals, no?
If a malicious application can map a peripheral, you have more
problems than crashing the machine, which is annoying but _nothing_
compared to the exposure of confidential data.
dcbt can improve performance in some cases, and the bug does not
affect an application which only has access to memory with default
attributes (write-back caching).
But maybe I miss something.
Gabriel
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-17 15:12 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
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 [this message]
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=20031117151246.GA31680@iram.es \
--to=paubert@iram.es \
--cc=adrian@humboldt.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
/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).