topic IPCF is non-functional after the Linux kernel is locked down. in S32G

IPCF is non-functional after the Linux kernel is locked down.

Jeff-CF-Huang — Mon, 06 Jan 2025 06:37:59 GMT

Hi Sir,

IPCF is non-functional after the Linux kernel is locked down.

Is there an alternative way to resolve it?

Best regards,

Jeff Huang

Re: IPCF is non-functional after the Linux kernel is locked down.

Joey_z — Mon, 06 Jan 2025 10:53:16 GMT

hi，Jeff-CF-Huang

In order to provide better support,can you provide more information?

Do you use custom boards?If not ,is it an RDB or EVB board?In addition ,which version of IPCF and BSP do you use?

According to your output information,There may be a conflict in the shared memory that IPCF tries to access.Do you follow the operation implemented by AN13750?

Joey

Re: IPCF is non-functional after the Linux kernel is locked down.

Jeff-CF-Huang — Tue, 07 Jan 2025 05:16:19 GMT

Hi Joey,

The IPCF functions correctly when the lockdown feature is disabled.

The kernel enables LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY to enhance security by blocking access to /dev/mem and /dev/kmem, which could otherwise allow reading or writing to kernel memory.

This issue persists consistently, regardless of the IPCF or BSP version.

Best regards,
Jeff Huang

Re: IPCF is non-functional after the Linux kernel is locked down.

Joey_z — Sun, 12 Jan 2025 12:33:46 GMT

Hi,Jeff-CF-Huang

Sorry for the late reply.

You should check if there is a conflict between the memory specified when the lockdown feature is enabled and the memory set by IPCF. If there is a conflict, you need to change it to a different address.

Joey