From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Roberto Sassu <roberto.sassu@huawei.com>
To: <zohar@linux.ibm.com>, <tiwai@suse.de>
Cc: <linux-integrity@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ima: Directly assign the ima_default_policy pointer to ima_rules
Date: Fri, 05 Jun 2020 14:10:57 +0000 [thread overview]
Message-ID: <20200605141057.D1F7A2086A@mail.kernel.org> (raw)
In-Reply-To: <20200603150821.8607-1-roberto.sassu@huawei.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 07f6a79415d7 ("ima: add appraise action keywords and default rules").
The bot has tested the following trees: v5.6.15, v5.4.43, v4.19.125, v4.14.182, v4.9.225, v4.4.225.
v5.6.15: Build OK!
v5.4.43: Build OK!
v4.19.125: Build OK!
v4.14.182: Failed to apply! Possible dependencies:
Unable to calculate
v4.9.225: Failed to apply! Possible dependencies:
Unable to calculate
v4.4.225: Failed to apply! Possible dependencies:
38d859f991f3 ("IMA: policy can now be updated multiple times")
95ee08fa373b ("ima: require signed IMA policy")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
prev parent reply other threads:[~2020-06-05 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 15:08 [PATCH 1/2] ima: Directly assign the ima_default_policy pointer to ima_rules Roberto Sassu
2020-06-03 15:08 ` [PATCH 2/2] ima: Call ima_calc_boot_aggregate() in ima_eventdigest_init() Roberto Sassu
2020-06-03 22:03 ` Mimi Zohar
2020-06-04 19:12 ` Bruno Meneguele
2020-06-04 19:35 ` Mimi Zohar
2020-06-04 19:57 ` Bruno Meneguele
2020-06-05 14:10 ` Sasha Levin
2020-06-03 21:30 ` [PATCH 1/2] ima: Directly assign the ima_default_policy pointer to ima_rules Mimi Zohar
2020-06-05 14:10 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200605141057.D1F7A2086A@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-integrity@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).