Article <uu0kt1$2nr9j$1@dont-email.me>

Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <uu0kt1$2nr9j$1@dont-email.me>

Deutsch English Français Italiano

<uu0kt1$2nr9j$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Thomas Koenig <tkoenig@netcologne.de>
Newsgroups: comp.arch
Subject: Re: Another security vulnerability
Date: Wed, 27 Mar 2024 08:20:49 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <uu0kt1$2nr9j$1@dont-email.me>
References: <utpoi2$b6to$1@dont-email.me>
 <2024Mar25.082534@mips.complang.tuwien.ac.at>
 <20240326192941.0000314a@yahoo.com>
Injection-Date: Wed, 27 Mar 2024 08:20:49 +0100 (CET)
Injection-Info: dont-email.me; posting-host="d28ef1cdb2468220a3cbbc5a3023845a";
	logging-data="2878771"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19Fxskp7Jpr69AahD51R20pwpZKkuGzrKc="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:mr9uiTWdZONjAJLt6oNNWQoqnx0=
Bytes: 1539

Michael S <already5chosen@yahoo.com> schrieb:

> In case you missed it, the web page contains link to pdf:
> https://gofetch.fail/files/gofetch.pdf

Looking the paper, it seems that a separate "load value" instruction
(where it is guaranteed that no pointer prefetching will be done)
could fix this particular issue.  Compilers know what type is being
loaded from memory, and could issue the corresponding instruction.
This would not impact performance.

Only works for new versions of an architecture, and supporting
compilers, but no code change would be required.  And, of course,
it would eat up opcode space.