All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	linux-integrity@vger.kernel.org
Subject: Re: [RFC PATCH] ima-evm-utils: Add some tests for evmctl
Date: Thu, 25 Jul 2019 21:03:04 -0400	[thread overview]
Message-ID: <1564102984.4245.199.camel@linux.ibm.com> (raw)
In-Reply-To: <20190725153823.dz6brcvoojum47dz@altlinux.org>

On Thu, 2019-07-25 at 18:38 +0300, Vitaly Chikunov wrote:
> Mimi,
> 
> On Thu, Jul 25, 2019 at 10:46:31AM -0400, Mimi Zohar wrote:
> > On Thu, 2019-07-25 at 09:18 +0300, Vitaly Chikunov wrote:
> > > Run `make check' to execute the tests.
> > > Currently only ima_hash, ima_sign (v2), and ima_verify are tested.
> > > 
> > > Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> > 
> > Nice!  As much as I would like to include this patch in this release,
> > let's hold off and add it to the next release.
> 
> You may include it if you wish, this should work good as is (over my
> latest patches).

Yes, it applies cleanly on top of the other patches.
> 
> > Reviewing shorter patches is a lot easier, at least for me.  Could you
> > break this patch up?  Perhaps by defining the tests separately, and
> > then adding the autotools support to run the test afterwards?
> 
> This is just tests, so they don't alter any other code, don't produce
> user visible features, and don't complicate anything. Each file inside
> of the patch could be understood separately.

I understand that.  However, without comments, with short function
names, and single letter variable names, makes reviewing the code more
difficult than needed.

Mimi


  reply	other threads:[~2019-07-26  1:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  6:18 [RFC PATCH] ima-evm-utils: Add some tests for evmctl Vitaly Chikunov
2019-07-25 14:46 ` Mimi Zohar
2019-07-25 15:38   ` Vitaly Chikunov
2019-07-26  1:03     ` Mimi Zohar [this message]
2019-07-25 21:58 ` Bruno E. O. Meneguele
2019-07-25 22:31   ` Vitaly Chikunov
2019-07-26 13:07 ` Petr Vorel
2019-07-28  4:53   ` Vitaly Chikunov

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=1564102984.4245.199.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=vt@altlinux.org \
    --cc=zohar@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.