linux-kernel - Adding module support for __ro_after

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGXu5jLGX5zp3KbynNsr=HvnUiG9r-U1tDMzyyRiXp1vsQw11A@mail.gmail.com>
Date:	Fri, 3 Jun 2016 11:46:29 -0700
From:	Kees Cook <keescook@...gle.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Laura Abbott <labbott@...oraproject.org>
Subject: Adding module support for __ro_after_init

Hi Rusty,

I'd love to get your thoughts on the best way to support
__ro_after_init markings for modules. Are the r/o markings done after
module __init runs? If so, this should make things easy, and then we
just need to move .data..ro_after_init into .rodata at link time. If
not, then we'd need to explicitly make this section read-only after
_init.

Thanks!

-Kees

-- 
Kees Cook
Chrome OS & Brillo Security