[PATCH v2 2/8] ima: Switch to ima_hash_algo for boot aggregate
Mimi Zohar
zohar at linux.ibm.com
Thu Feb 6 12:17:06 UTC 2020
On Thu, 2020-02-06 at 09:36 +0000, Roberto Sassu wrote:
> > Hi Roberto,
> >
> > On Wed, 2020-02-05 at 11:33 +0100, Roberto Sassu wrote:
> >
> > <snip>
> >
> > > Reported-by: Jerry Snitselaar <jsnitsel at redhat.com>
> > > Suggested-by: James Bottomley
> > <James.Bottomley at HansenPartnership.com>
> > > Signed-off-by: Roberto Sassu <roberto.sassu at huawei.com>
> > > Cc: stable at vger.kernel.org
> >
> > Cc'ing stable resulted in Sasha's automated message. If you're going
> > to Cc stable, then please include the stable kernel release (e.g. Cc:
> > stable at vger.kernel.org # v5.3). Also please include a "Fixes" tag.
> > Normally only bug fixes are backported.
>
> Ok, will add the kernel version. I also thought which commit I should
> mention in the Fixes tag. IMA always read the SHA1 bank from the
> beginning. I could mention the patch that introduces the new API
> to read other banks, but I'm not sure. What do you think?
This patch is dependent on nr_allocated_banks. Please try applying
this patch to the earliest stable kernel with the commit that
introduces nr_allocated_banks and test to make sure it works properly.
thanks,
Mimi
More information about the Linux-security-module-archive
mailing list