> -----Original Message----- > From: owner-linux-security-module@xxxxxxxxxxxxxxx [mailto:owner-linux- > security-module@xxxxxxxxxxxxxxx] On Behalf Of Mimi Zohar > Sent: Wednesday, February 5, 2020 10:01 PM > To: Roberto Sassu <roberto.sassu@xxxxxxxxxx>; > James.Bottomley@xxxxxxxxxxxxxxxxxxxxx; > jarkko.sakkinen@xxxxxxxxxxxxxxx > Cc: linux-integrity@xxxxxxxxxxxxxxx; linux-security-module@xxxxxxxxxxxxxxx; > linux-kernel@xxxxxxxxxxxxxxx; Silviu Vlasceanu > <Silviu.Vlasceanu@xxxxxxxxxx>; stable@xxxxxxxxxxxxxxx > Subject: Re: [PATCH v2 2/8] ima: Switch to ima_hash_algo for boot > aggregate > > Hi Roberto, > > On Wed, 2020-02-05 at 11:33 +0100, Roberto Sassu wrote: > > <snip> > > > Reported-by: Jerry Snitselaar <jsnitsel@xxxxxxxxxx> > > Suggested-by: James Bottomley > <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> > > Signed-off-by: Roberto Sassu <roberto.sassu@xxxxxxxxxx> > > Cc: stable@xxxxxxxxxxxxxxx > > 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@xxxxxxxxxxxxxxx # 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? Thanks Roberto
