From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: zohar@linux.ibm.com, stephen.smalley.work@gmail.com,
paul@paul-moore.com, tusharsu@linux.microsoft.com,
ltp@lists.linux.it, linux-integrity@vger.kernel.org
Subject: Re: [PATCH v1 0/1] ima: Add test for selinux measurement
Date: Wed, 30 Sep 2020 07:26:20 -0700 [thread overview]
Message-ID: <281c5fa0-8d3a-0812-9d20-a5c7ee4f7666@linux.microsoft.com> (raw)
In-Reply-To: <20200929052340.GA4976@dell5510>
On 9/28/20 10:23 PM, Petr Vorel wrote:
> Hi Lakshmi,
>
> Thanks for your patch. FYI I'll try to have look ASAP, but as there is LTP
> freeze and work needed to review fixes before release I'll probably review this
> after the release (1, max. 2 weeks).
>
> Could you please have a look at fix planned to be part of the release?
> https://patchwork.ozlabs.org/project/ltp/list/?series=204230
>
Will do Petr.
>
>> New functionality is being added to IMA to measure data provided by
>> kernel components. With this feature, IMA policy can be set to enable
>> measuring data provided by Linux Security Modules (LSM). Currently one
>> such LSM namely selinux is being updated to use this functionality.
>> This new functionality needs test automation in LTP.
>
>> This patch set adds tests which verify that the IMA subsystem correctly
>> measures the data provided by selinux.
>
>> This patch is based on
>> commit 286401a1c1f3 ("thp04: Add linux tag")
>> in "master" branch in https://github.com/linux-test-project/ltp
>
>> This patch is dependent on the following patch series in LTP
>> https://patchwork.kernel.org/patch/11802771/
> I put link to LTP patchwork to avoid the confusion.
> https://patchwork.ozlabs.org/project/ltp/list/?series=204486
Thanks. On the next update I'll add the LTP patchwork URL.
>
>> This series needs a kernel built on the following repo/branch/patches:
>> repo: https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
>> branch: next
>> commit 8861d0af642c ("selinux: Add helper functions to get and set checkreqprot")
> Thanks for adding this info. It'd be great if it were part of kernel commit
> message and also added as a comment in the test itself (we don't want to get it
> lost).
>
> BTW LTP has 2 kind ways of handling of kernel versions:
>
> * fixes which are meant to be backported to the stable trees:
> In C API it looks like (here also with CVE entry):
> https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/bpf/bpf_prog03.c#L187
> .tags = (const struct tst_tag[]) {
> {"linux-git", "95a762e2c8c9"},
> {"CVE", "2017-16995"},
> {}
> This is not part of shell API, but I'll add it after the release. Thus we don't
> want to loose this info.
>
> * new kernel features, which are likely not to be backported
> You either have some way to detect this feature is presented (ideally) or you
> specify kernel version since it should be run
> This is used in shell API as:
> https://github.com/linux-test-project/ltp/blob/master/testcases/network/tcp_cc/bbr02.sh#L8
> TST_MIN_KVER="4.13"
Thanks for the info.
-lakshmi
>
>> And the following patch series should be applied in the following order:
>> 1, https://patchwork.kernel.org/patch/11709527/
>> 2, https://patchwork.kernel.org/patch/11795559/
>> 3, https://patchwork.kernel.org/patch/11801525/
>> 4, https://patchwork.kernel.org/patch/11801585/
>
prev parent reply other threads:[~2020-09-30 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:47 [PATCH v1 0/1] ima: Add test for selinux measurement Lakshmi Ramasubramanian
2020-09-28 19:47 ` [PATCH v1 1/1] " Lakshmi Ramasubramanian
2020-12-18 18:37 ` Petr Vorel
2020-12-22 18:37 ` Lakshmi Ramasubramanian
2020-12-22 19:50 ` Petr Vorel
2020-12-22 21:05 ` Lakshmi Ramasubramanian
2020-09-29 5:23 ` [PATCH v1 0/1] " Petr Vorel
2020-09-30 14:26 ` Lakshmi Ramasubramanian [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=281c5fa0-8d3a-0812-9d20-a5c7ee4f7666@linux.microsoft.com \
--to=nramas@linux.microsoft.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=paul@paul-moore.com \
--cc=pvorel@suse.cz \
--cc=stephen.smalley.work@gmail.com \
--cc=tusharsu@linux.microsoft.com \
--cc=zohar@linux.ibm.com \
/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).