From: Petr Vorel <pvorel@suse.cz>
To: George Wilson <gcwilson@us.ibm.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [RFC PATCH v2 3/4] ima/ima_boot_aggregate: Increase MAX_EVENT_SIZE to 8k
Date: Thu, 29 Mar 2018 08:18:16 +0200 [thread overview]
Message-ID: <20180329061816.GB31604@x230> (raw)
In-Reply-To: <OF557260E5.C2BA817A-ON8625825D.007ABFC1-8625825D.007AFB67@notes.na.collabserv.com>
Hi George,
> > Is there a way of making this value system dependent? On my
> > laptop this is fine, but for PowerVM w/TPM 1.2 I've been told this is
> > too small.
> Why not follow the spec? PowerVM has enormous events because they
> were allowed by the 1.2 spec. The 2.0 spec recommends 1M so I think
> they should be at least 1M. Because they're large, they should really
> be dynamically allocated.
Make sense. Lets try 1M.
Thanks a lot for your input.
Kind regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 3/4] ima/ima_boot_aggregate: Increase MAX_EVENT_SIZE to 8k
Date: Thu, 29 Mar 2018 08:18:16 +0200 [thread overview]
Message-ID: <20180329061816.GB31604@x230> (raw)
In-Reply-To: <OF557260E5.C2BA817A-ON8625825D.007ABFC1-8625825D.007AFB67@notes.na.collabserv.com>
Hi George,
> > Is there a way of making this value system dependent? Â On my
> > laptop this is fine, but for PowerVM w/TPM 1.2 I've been told this is
> > too small.
> Why not follow the spec? PowerVM has enormous events because they
> were allowed by the 1.2 spec. The 2.0 spec recommends 1M so I think
> they should be at least 1M. Because they're large, they should really
> be dynamically allocated.
Make sense. Lets try 1M.
Thanks a lot for your input.
Kind regards,
Petr
next prev parent reply other threads:[~2018-03-29 6:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:57 [RFC PATCH v2 0/4] Rewrite tests into new API + fixes Petr Vorel
2018-03-14 15:57 ` [LTP] " Petr Vorel
2018-03-14 15:57 ` [RFC PATCH v2 1/4] security/ima: " Petr Vorel
2018-03-14 15:57 ` [LTP] " Petr Vorel
2018-03-14 16:32 ` Petr Vorel
2018-03-14 16:32 ` [LTP] " Petr Vorel
2018-03-27 19:12 ` Mimi Zohar
2018-03-27 19:12 ` [LTP] " Mimi Zohar
2018-03-29 8:59 ` Petr Vorel
2018-03-29 8:59 ` [LTP] " Petr Vorel
2018-04-10 15:56 ` Mimi Zohar
2018-04-10 15:56 ` [LTP] " Mimi Zohar
2018-04-11 19:03 ` Petr Vorel
2018-04-11 19:03 ` [LTP] " Petr Vorel
2018-04-11 20:03 ` Mimi Zohar
2018-04-11 20:03 ` [LTP] " Mimi Zohar
2018-03-14 15:57 ` [RFC PATCH v2 2/4] security/ima: Run measurements after policy Petr Vorel
2018-03-14 15:57 ` [LTP] " Petr Vorel
2018-03-14 15:57 ` [RFC PATCH v2 3/4] ima/ima_boot_aggregate: Increase MAX_EVENT_SIZE to 8k Petr Vorel
2018-03-14 15:57 ` [LTP] " Petr Vorel
2018-03-27 19:44 ` Mimi Zohar
2018-03-27 19:44 ` [LTP] " Mimi Zohar
2018-03-27 22:23 ` George Wilson
2018-03-29 6:18 ` Petr Vorel [this message]
2018-03-29 6:18 ` Petr Vorel
2018-03-14 15:57 ` [RFC PATCH v2 4/4] ima/tpm: Various fixes Petr Vorel
2018-03-14 15:57 ` [LTP] " Petr Vorel
2018-03-26 22:31 ` [RFC PATCH v2 0/4] Rewrite tests into new API + fixes Mimi Zohar
2018-03-26 22:31 ` [LTP] " Mimi Zohar
2018-03-27 9:22 ` Petr Vorel
2018-03-27 9:22 ` [LTP] " 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=20180329061816.GB31604@x230 \
--to=pvorel@suse.cz \
--cc=gcwilson@us.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--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.