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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 24 May 2020 19:57:48 -0400
From:   Arvind Sankar <>
To:     Fangrui Song <>
Cc:     Arvind Sankar <>,
        Thomas Gleixner <>,
        Ingo Molnar <>, Borislav Petkov <>,
        "H. Peter Anvin" <>,,
        Nick Desaulniers <>,
        Dmitry Golovin <>,,
        Ard Biesheuvel <>,
        Masahiro Yamada <>,
        Daniel Kiper <>,
        Kees Cook <>,
Subject: Re: [PATCH 4/4] x86/boot: Check that there are no runtime relocations

On Sun, May 24, 2020 at 04:36:07PM -0700, Fangrui Song wrote:
> `grep -qF .rel.local` from 98f78525371b55ccd1c480207ce10296c72fa340
> may be incorrect.. None of these synthesized dynamic relocation sections is
> called *.rel.local* ...
> (it probably wanted to name or
> Reviewed-by: Fangrui Song <>

At least from gcc you get .data.rel.local sections if you have, for eg:
	struct { void *p; } foo = { .p = &bar };
where bar is defined in the same file. These aren't relocation sections,
foo is actually placed in the .data.rel.local section instead of .data.

But yeah, it's incomplete, you wouldn't catch it if bar was external
(foo goes in .data.rel) or foo was const (foo goes in*).

Powered by blists - more mailing lists