Re: [PATCH v2 1/3] powerpc/fadump: make is_fadump_active() visible for exporting vmcore

On 09/06/23 at 12:06am, Hari Bathini wrote: > Include asm/fadump.h in asm/kexec.h to make it visible while exporting > vmcore. Also, update is_fadump_active() to return boolean instead of > integer for better readability. The change will be used in the next > patch to ensure vmcore is exported when

Re: [PATCH v2 4/9] mm: vmalloc: Remove global vmap_area_root rb-tree

Add Kazu and Lianbo to CC, and kexec mailing list On 08/29/23 at 10:11am, Uladzislau Rezki (Sony) wrote: > Store allocated objects in a separate nodes. A va->va_start > address is converted into a correct node where it should > be placed and resided. An addr_to_node() function is used > to do a pr

Re: [RFC] IMA Log Snapshotting Design Proposal - aggregate

On 9/1/2023 6:06 PM, Tushar Sugandhi wrote: On 8/30/23 11:12, Ken Goldman wrote: On 8/1/2023 3:12 PM, Sush Shringarputale wrote: - A user-mode process will trigger the snapshot by opening a file in SysFS    say /sys/kernel/security/ima/snapshot (referred to as sysk_ima_snapshot_file    here

Re: [RFC] IMA Log Snapshotting Design Proposal - network bandwidth

On 9/1/2023 5:20 PM, Tushar Sugandhi wrote: Thanks a lot Ken for looking at the proposal, and sharing your thoughts. On 8/30/23 11:06, Ken Goldman wrote: On 8/1/2023 3:12 PM, Sush Shringarputale wrote: In addition, a large IMA log can add pressure on the network bandwidth when the attesta

Re: [RFC] IMA Log Snapshotting Design Proposal - unseal

On 9/1/2023 5:22 PM, Tushar Sugandhi wrote: On 8/30/23 12:12, Ken Goldman wrote: On 8/1/2023 3:12 PM, Sush Shringarputale wrote: For remote attestation to work, the service will need to know how to  validate the snapshot_aggregate entry in the IMA log.  It will have to read the PCR values

[PATCH 1/3] proc/vmcore: Do not map unaccepted memory

Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Do not map unaccepted memory because it can cause the guest to fail. For /proc/vmcore, which is read-on

[PATCH 3/3] /dev/mem: Do not map unaccepted memory

Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Do not map unaccepted memory because it can cause the guest to fail. For /dev/mem, this means a read of

Re: [PATCH v2 3/8] crash_core: change parse_crashkernel() to support crashkernel=,high|low parsing

On 2023/9/5 16:29, Baoquan He wrote: > On 09/04/23 at 10:47am, Leizhen (ThunderTown) wrote: >> >> >> On 2023/9/1 17:49, Baoquan He wrote: > + > + *high = true; > + } else if (ret || !*crash_size) { This check can be moved outside of #ifdef. Because even '!high', it's >>

[PATCH 0/3] Do not map unaccepted memory

Hi Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Plug a few gaps where RAM is exposed without checking if it is unaccepted memory. Adrian Hunter (3

[PATCH 2/3] proc/kcore: Do not map unaccepted memory

Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Do not map unaccepted memory because it can cause the guest to fail. For /proc/kcore, which is read-onl