[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <161cb1b4-ccdc-fba1-c272-45b8ed261cb2@jonmasters.org>
Date: Tue, 25 Apr 2017 03:00:42 -0400
From: Jon Masters <jcm@...masters.org>
To: Kees Cook <keescook@...omium.org>, Jessica Yu <jeyu@...hat.com>
Cc: Rusty Russell <rusty@...tcorp.com.au>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Heinrich Schuchardt <xypron.glpk@....de>,
Nicholas Piggin <npiggin@...il.com>,
Chris Metcalf <cmetcalf@...lanox.com>,
linux-kernel@...r.kernel.org,
Lucas De Marchi <lucas.demarchi@...el.com>
Subject: Re: [PATCH v2 2/2] module: Add module name to modinfo
On 04/21/2017 06:35 PM, Kees Cook wrote:
> Accessing the mod structure (e.g. for mod->name) prior to having completed
> check_modstruct_version() can result in writing garbage to the error logs
> if the layout of the mod structure loaded from disk doesn't match the
> running kernel's mod structure layout. This kind of mismatch will become
> much more likely if a kernel is built with different randomization seed
> for the struct layout randomization plugin.
>
> Instead, add and use a new modinfo string for logging the module name.
+Lucas - probably something that the modinfo kmod utility should track.
Jon.
Powered by blists - more mailing lists