[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202112020012.8B4C205@keescook>
Date: Thu, 2 Dec 2021 00:14:18 -0800
From: Kees Cook <keescook@...omium.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Luis Chamberlain <mcgrof@...nel.org>, Jessica Yu <jeyu@...nel.org>,
linux-kernel@...r.kernel.org, linux-modules@...r.kernel.org
Subject: Re: [PATCH] module: add in-kernel support for decompressing
On Wed, Dec 01, 2021 at 12:19:08PM -0800, Dmitry Torokhov wrote:
> On Wed, Dec 01, 2021 at 11:24:35AM -0800, Kees Cook wrote:
> > On Sat, Nov 27, 2021 at 09:48:22PM -0800, Dmitry Torokhov wrote:
> > > /* Flags for sys_finit_module: */
> > > #define MODULE_INIT_IGNORE_MODVERSIONS 1
> > > #define MODULE_INIT_IGNORE_VERMAGIC 2
> > > +#define MODULE_INIT_COMPRESSED_DATA 4
> >
> > bikeshedding: adding "_DATA" seems redundant/misleading? The entire
> > module is compressed, so maybe call it just MODULE_INIT_COMPRESSED ?
>
> OK, or maybe MODULE_INIT_COMPRESSED_FILE since we are indeed dealing
> with a file?
Sounds good to me! :)
As far as my tangent on using the crypto subsystem, I think that looks
like a long path, so your existing routines are likely the right place
to start. I still wonder if it might be able to use of the "acomp" API
instead of calling directly into the specific decompressor.
--
Kees Cook
Powered by blists - more mailing lists