linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Henrie <alexh@vpitech.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, alexhenrie24@gmail.com
Subject: Re: [PATCH] ima: add gid support
Date: Wed, 8 Sep 2021 15:20:54 -0600	[thread overview]
Message-ID: <20210908152054.b6483142c7fce15f2bf01548@vpitech.com> (raw)
In-Reply-To: <ab00a38ebd268a67eae306a368cd94964a06f0ba.camel@linux.ibm.com>

On Wed, 01 Sep 2021 10:54:21 -0400
Mimi Zohar <zohar@linux.ibm.com> wrote:

> Hi Alex,
> 
> On Tue, 2021-08-31 at 20:12 -0600, Alex Henrie wrote:
> > Hello, could I get some feedback on this patch? Are there any
> > objections to including it upstream?
> 
> Conceptually I don't have a problem with the patch, but I'd also like a
> test to go with it.  
> 
> Roberto posted "ima-evm-utils: Add UML support and tests for EVM
> portable signatures", which introduces using UML (User Mode Linux) for
> testing new kernel features, which, unfortunately, still needs to be
> reviewed and upstreamed.  (Hint, hint help with reviewing.]
> 
> Another option is to define an LTP test.   In either case, a custom IMA
> policy would be defined in terms of a loopback mounted filesystem to
> avoid affecting the entire system.
> 
> I'd appreciate your re-basing and re-posting this patch.
> 
> thanks,
> 
> Mimi
> 

Thanks for the feedback! The UML tests are intriguing and I will be
interested to see how they work out. However, I think the tests for
this particular patch fit better with the existing LTP tests. I will
send a rebased kernel patch and an LTP patch.

-Alex

      reply	other threads:[~2021-09-08 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 22:20 [PATCH] ima: add gid support Alex Henrie
2021-09-01  2:12 ` Alex Henrie
2021-09-01 14:54   ` Mimi Zohar
2021-09-08 21:20     ` Alex Henrie [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=20210908152054.b6483142c7fce15f2bf01548@vpitech.com \
    --to=alexh@vpitech.com \
    --cc=alexhenrie24@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --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).