CONFIG_DM_CRYPT missing in Torizon OS 7

Hello Toradex
In Torizon OS7 there is no Kernel modul CONFIG_DM_CRYPT. We use that in Torizon OS6 to manage luks partitions. Now we wanna upgrade our devices to Torizon OS7. Can you please bring CONFIG_DM_CRYPT into Torizon OS7? Thanks.

Torizon OS7, txd-info:

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           6.6.23-7.0.0-g558ba3740880 #1-Torizon SMP PREEMPT Wed Sep 25 11:25:16 UTC 2024
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/6974f2fabaf10642395d3004fa4c3ecfd15476a29f9537e91f311d05665a9e6b/0
Distro name:              NAME="Torizon OS"
Distro version:           VERSION_ID=7.0.0-build.1
Hostname:                 verdin-imx8mm-15361223
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Mini custom
Toradex version:          0086 V1.1#26
Serial number:            15361223
Processor arch:           aarch64
------------------------------------------------------------

Torizon OS6, txd-info:

Software summary
------------------------------------------------------------
Bootloader:               U-Boot
Kernel version:           5.15.148-6.8.0+git.8c5c2dcbf6ba #1-TorizonCore SMP PREEMPT Tue Aug 6 10:01:59 UTC 2024
Kernel command line:      root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/4ce5201e7c4599e052b0e0311db6a4875e04be881fa94b115c316d1ff169bc2a/0
Distro name:              NAME="TorizonCore"
Distro version:           VERSION_ID=6.8.0-build.22
Distro variant:           VARIANT="Docker"
Hostname:                 verdin-imx8mm-15331494
------------------------------------------------------------

Hardware info
------------------------------------------------------------
HW model:                 Toradex Verdin iMX8M Mini
Toradex version:          0086 V1.1#26
Serial number:            15331494
Processor arch:           aarch64
------------------------------------------------------------

Hi @pitschen !

I just checked the toradex-kernel-cache repository on scarthgap-7.x.y branch (used on Torizon OS 7) and the CONFIG_DM_CRYPT is enabled as kernel module just like it is on kirkistone-6.x.y branch (used on Torizon OS 6).

Torizon OS 6:

Torizon OS 7:

From the links above, we see that the CONFIG_DM_CRYPT remains the same between Torizon OS 6 and 7.

Could you please execute the following command on both of your images (Torizon OS 6 and 7) and share the outputs, so we can check if is enabled on your images?

sudo grep DM_CRYPT /proc/config.gz

Best regards,

Torizon OS6:

torizon@verdin-imx8mm-15331494:~$ sudo grep DM_CRYPT /proc/config.gz
torizon@verdin-imx8mm-15331494:~$ 

=> I always check it with following:

torizon@verdin-imx8mm-15331494:~$ zcat /proc/config.gz | grep CONFIG_DM_CRYPT
CONFIG_DM_CRYPT=m

Torizon OS7:

torizon@verdin-imx8mm-15361223:~$ sudo grep DM_CRYPT /proc/config.gz
torizon@verdin-imx8mm-15361223:

=> check with zcat

torizon@verdin-imx8mm-15361223:~$ zcat /proc/config.gz | grep CONFIG_DM_CRYPT
torizon@verdin-imx8mm-15361223:~$

And I see the missing configuration also in my application in Torizon OS7:
After creating a luks partition with cryptsetup luksFormat I cannot open it:

root@verdin-imx8mm-15361223:/var/rootdirs/home/torizon#  cryptsetup open /dev/mmcblk1p1 foo   
Cannot initialize device-mapper. Is dm_mod kernel module loaded?

Br.

Hi @pitschen!

My mistake. You are totally right. zcat is the correct way.

Just to be sure: you are using a “vanilla” Torizon OS image, right? Or you built it yourself?

Best regards,

We use
https://artifacts.toradex.com:443/artifactory/torizoncore-oe-prod-frankfurt/scarthgap-7.x.y/release/1/verdin-imx8mm/torizon/torizon-docker/oedeploy/torizon-docker-verdin-imx8mm-Tezi_7.0.0%2Bbuild.1.tar

And then we build it with our customization with torizoncorebuilder.

Br.

Hi @pitschen !

I brought it up internally.

I will send you a message here as soon as I have some update.

Thank you for reporting this.

If this deeply affects your project, please let us know your timeline so I can inform the team.

Best regards,

Hi @pitschen !

Although it is complex to define how long it my take to have it enabled, I was informed that it should be available in 1 week.

If we have any news related to this I will let you know.

Best regards,

Hello Henrique

Thanks for support. Br.

Hi @pitschen !

The fix was done and it is available on the latest quarterly release Torizon OS 7.1.0:

Could you please try it on your side?

Best regards,

Hi Henrique

I tested it, works! Thanks for support.
Br.

Hi @pitschen !

That’s great!

Thanks for the reply and for marking the solution!

Have a nice day!