y.mi. (she/they)

I have removed the trigger of these messages from the code and recompiled the module. For now, my devices are working fine. I will post update if something happens.

As a temporary fix, I created a patch which you can apply to your 6.8-rcX kernel to make VDO compile successfully. It was tested on Linux kernel `6.8-rc4-rt4`. The patch...

Sorry, the fix was to first replay the journal using a machine with old version of KVDO. (And shut down the vdo cleanly). Thanks for the update and integration with...

Unfortunately, I have to reopen the issue because there is likely a bug related to the new version (in-kernel) of KVDO. More specifically, **once you attempt to bring up a...

A one more thing to note: the VDO stats are broken (in-kernel KVDO, the names of my devices are replaced with "****") ``` $ su -c vdostats Device 1k-blocks Used...

### Fix for the broken devices Sorry again, it turned out that the broken dirty devices were **easily fixable by a forced «rebuild»**. They are now R/W, give no errors,...

Hi @rhawalsh, thanks for your reply! I was using this version before: ``` kvdo: modprobe: loaded version 8.2.3.3 ``` After that, I moved (from linux-6.8) to linux 6.9-rc2 with it's...

Thanks for the attention, @rhawalsh. The forced rebuild was done on the 6.9-rc2 kernel. After that, my devices started working, so I stay on the new version.

@g2p Could I just ask, how do you make the kernel show the relevant source files in backtraces? And the `All code` thing? Is it some patch to kernel, or...

@koverstreet have you thought about getting `current->signal->tty` in the mount context, and interacting with it by `current->signal->tty->driver->ops->...` functions? It wouldn't require any "integration with systemd". I used it in my...