[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9714e2824b35d12ee2f8ad70d65d8c9230be86e4.camel@linux.ibm.com>
Date: Fri, 28 Jan 2022 09:33:55 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Roberto Sassu <roberto.sassu@...wei.com>,
"Guozihua (Scott)" <guozihua@...wei.com>,
Jonathan Corbet <corbet@....net>
Cc: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
wangweiyang <wangweiyang2@...wei.com>,
Xiujianfeng <xiujianfeng@...wei.com>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>
Subject: Re: [RESEND][PATCH] Documentation: added order requirement for
ima_hash=
On Fri, 2022-01-28 at 10:24 +0000, Roberto Sassu wrote:
> > From: Mimi Zohar [mailto:zohar@...ux.ibm.com]
> > Sent: Wednesday, January 26, 2022 1:48 PM
> > On Wed, 2022-01-26 at 15:41 +0800, Guozihua (Scott) wrote:
> > >
> > >
> > > The main issue lies in ima_template_desc_current called by hash_setup,
> > > which does not just read ima_template global variable, but also tries to
> > > set it if that hasn't been done already. Causing ima_template_setup to quit.
> >
> > Right, which calls ima_init_template_list(). So part of the solution
> > could be to conditionally call ima_init_template_list()
> > in ima_template_setup().
> >
> > - if (ima_template)
> > - return 1;
> > -
> > - ima_init_template_list();
> > + if (!ima_template
> > + ima_init_template_list();
>
>
> is it still necessary to call ima_init_template_list() in
> template_setup()? I saw it is called in init_ima().
All of these options are at __setup().
thanks,
Mimi
Powered by blists - more mailing lists