From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0e68acc61f376dc0c9b47eda01e70bff@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bounds checking bug in fcall(2) functions
From: Charles Forsyth <forsyth@terzarima.net>
Date: Fri,  9 Nov 2007 23:41:42 +0000
In-Reply-To: <815f4e4b0711091501v53a37569x5c5f576623fb9547@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: f17f43de-ead2-11e9-9d60-3106f5b1d025

> (But it could be a problem if the buffer is
> right at the end of the virtual memory space :). Sorry about the buggy ...

that will be a problem if the hardware is sloppy, but it would be true regardless how
you wrote the test (because it's the resulting prefetch addresses that then matter).
i think hardware designers now know about this problem (since it's fairly old)
but that probably hasn't stopped a few from not including it in the processor manual
but slipping it instead into the errata.