Hi Hari,
On 08/04/16 at 01:03am, Hari Bathini wrote:
> crashkernel parameter supports different syntaxes to specify the amount
> of memory to be reserved for kdump kernel. Below is one of the supported
> syntaxes that needs parsing to find the memory size to reserve, based on
> memory range:
>
>
Hari Bathini writes:
...
> /**
> * fadump_calculate_reserve_size(): reserve variable boot area 5% of System
> RAM
> *
> @@ -212,12 +262,17 @@ static inline unsigned long
> fadump_calculate_reserve_size(void)
> {
> unsigned long size;
>
> + /* sets fw_dump.reserve_bootvar */
> +
Hi Eric,
I have several questions about kdump and APIC mode.
specific issues at the end of the mail.
On Tue, 2016-08-02 at 09:26 -0500, Eric W. Biederman wrote:
> "Wei, Jiangang" writes:
>
> > Hi Eric,
> >
> > Thanks for your response.
> > But I have some different ideas...
>
> Apologies for n
Measurements carried across kexec need to be added to the IMA
measurement list, but should not prevent measurements of the newly
booted kernel from being added to the measurement list. This patch
adds support for allowing duplicate measurements.
The "boot_aggregate" measurement entry is the delimi
The TPM PCRs are only reset on a hard reboot. In order to validate a
TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list
of the running kernel must be saved and restored on boot. This patch
serializes the IMA measurement list in the binary_runtime_measurements
format.
Signed
The TPM PCRs are only reset on a hard reboot. In order to validate a
TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list
of the running kernel must be saved and then restored on the subsequent
boot.
The existing securityfs binary_runtime_measurements file conveniently
provide
From: Thiago Jung Bauermann
This patch uses the kexec buffer passing mechanism to pass the
serialized IMA binary_runtime_measurements to the next kernel.
Changelog:
- updated to call IMA functions (Mimi)
- move code from ima_template.c to ima_kexec.c (Mimi)
Signed-off-by: Thiago Jung Bauermann
In preparation for serializing the binary_runtime_measurements, this patch
maintains the amount of memory required.
Signed-off-by: Mimi Zohar
---
security/integrity/ima/Kconfig | 12 ++
security/integrity/ima/ima.h | 1 +
security/integrity/ima/ima_queue.c | 49 +++
The builtin and single custom templates are currently stored in an
array. In preparation for being able to restore a measurement list
containing multiple builtin/custom templates, this patch stores the
builtin and custom templates as a linked list. This will permit
defining more than one custom t
"Wei, Jiangang" writes:
> Hi Eric,
>
> I have several questions about kdump and APIC mode.
> specific issues at the end of the mail.
>
> On Tue, 2016-08-02 at 09:26 -0500, Eric W. Biederman wrote:
[snip]
>> For simplicity when MP support was first added, a few parts of early
>> bootup were left h
On Thursday 04 August 2016 03:15 PM, Michael Ellerman wrote:
Hari Bathini writes:
...
/**
* fadump_calculate_reserve_size(): reserve variable boot area 5% of System
RAM
*
@@ -212,12 +262,17 @@ static inline unsigned long
fadump_calculate_reserve_size(void)
{
unsigned long s
Hi Dave
Thanks for the review..
On Thursday 04 August 2016 02:56 PM, Dave Young wrote:
Hi Hari,
On 08/04/16 at 01:03am, Hari Bathini wrote:
crashkernel parameter supports different syntaxes to specify the amount
of memory to be reserved for kdump kernel. Below is one of the supported
syntax
> In your original email, you said that you cannot place the kernel
> at the address 0x0. Is this your problem, isn't it?
Not being able to put the kernel at 0 should not be considered a
restriction. The kernel is not mandated to start at 0 address. The tools
code was working fine till arm li
13 matches
Mail list logo
