From: Petr Vorel <pvorel@suse.cz>
To: Tushar Sugandhi <tusharsu@linux.microsoft.com>
Cc: zohar@linux.ibm.com, agk@redhat.com, snitzer@redhat.com,
gmazyland@gmail.com, nramas@linux.microsoft.com,
linux-integrity@vger.kernel.org, dm-devel@redhat.com,
ltp@lists.linux.it
Subject: Re: [PATCH v2 1/2] IMA: generalize key measurement tests
Date: Tue, 23 Feb 2021 23:38:51 +0100 [thread overview]
Message-ID: <YDWD+9dB8kx0ZPYR@pevik> (raw)
In-Reply-To: <28c14c80-660a-0f36-64ca-ae5230992032@linux.microsoft.com>
Hi Tushar,
> Thanks for your review.
> My sincere apologies for missing this email and not responding in time.
> The device mapper measurement work is being revisited - to cover aspects
> like more DM targets (not just dm-crypt), better memory management,
> more relevant attributes from the DM targets, other corner cases etc.
> Therefore, even though this patch, "1/2: generalize key measurement
> tests", would be useful for other tests; I will have to revisit the
> second patch, "2/2: dm-crypt measurements", to address the DM side changes I
> mentioned above.
> I will revisit this series, esp. testing the DM target measurements
> part, once the kernel work I mentioned above is close to completion.
> I will also address your feedback on patch #1 and #2 from v2 iteration
> at that time.
> Thanks again for your review and feedback.
I updated your patchset a bit and going to send it to ML.
Kind regards,
Petr
> Thanks,
> Tushar
next prev parent reply other threads:[~2021-02-23 22:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 3:56 [PATCH v2 0/2] IMA: Add test for dm-crypt measurement Tushar Sugandhi
2020-09-28 3:56 ` [PATCH v2 1/2] IMA: generalize key measurement tests Tushar Sugandhi
2020-12-21 23:05 ` Petr Vorel
2021-02-22 18:54 ` Tushar Sugandhi
2021-02-23 22:38 ` Petr Vorel [this message]
2020-09-28 3:56 ` [PATCH v2 2/2] IMA: Add test for dm-crypt measurement Tushar Sugandhi
2021-01-12 23:13 ` Petr Vorel
2021-05-06 9:14 ` Petr Vorel
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=YDWD+9dB8kx0ZPYR@pevik \
--to=pvorel@suse.cz \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=nramas@linux.microsoft.com \
--cc=snitzer@redhat.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).