lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 15 Sep 2021 12:18:58 -0700 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Guenter Roeck <linux@...ck-us.net> Cc: Richard Henderson <rth@...ddle.net>, Ivan Kokshaysky <ink@...assic.park.msu.ru>, Matt Turner <mattst88@...il.com>, "James E . J . Bottomley" <James.Bottomley@...senpartnership.com>, Helge Deller <deller@....de>, "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, alpha <linux-alpha@...r.kernel.org>, Geert Uytterhoeven <geert@...ux-m68k.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-parisc@...r.kernel.org, Netdev <netdev@...r.kernel.org>, Sparse Mailing-list <linux-sparse@...r.kernel.org> Subject: Re: [PATCH v2 0/4] Introduce and use absolute_pointer macro On Tue, Sep 14, 2021 at 8:52 PM Guenter Roeck <linux@...ck-us.net> wrote: > > This patch series introduces absolute_pointer() to fix the problem. > absolute_pointer() disassociates a pointer from its originating symbol > type and context, and thus prevents gcc from making assumptions about > pointers passed to memory operations. Ok, I've applied this to my tree. I note that the physical BOOT_PCB addresses in the alpha setup.h file might be useful for things like MILO in user space, but since I couldn't even find MILO sources any more, I couldn't really check. I suspect alpha is basically on life support and presumably nobody would ever compile a bootloader anyway, so it's unlikely to matter. If somebody does find any issues, we'll know better and we can ask where the user space sources are that might use that alpha setup.h file. Linus
Powered by blists - more mailing lists