On 6/24/22 08:43, Hannes Reinecke wrote:
Because Linbit is developing the DRBD driver outside the kernel, and it has diverged quite heavily from the in-kernel one. And having far more features to boot.
So just falling back to the in-kernel one is not making you any friends, especially not with existing installations.
Doing development outside the kernel for a driver already included in the kernel is absolutely the wrong thing to do! To me, this situation reeks of developer(s) getting bad reviews and forking the code into a separate project rather than doing the hard work of fixing the problem. As an example, look at the history of the Reiser 4 file system, which was derived from reiserfs! This behavior should not be rewarded by openSUSE. For maximum security, someone should update the in-kernel version following the standard patch submission and review procedures. As maintainer of the openSUSE version of VirtualBox, I am fully aware of the hazards of out-of-kernel drivers with lots of security holes. VB gets many, many CVE fixes each year. In this case, the value of the package warrants the use of VB; however, I would be pleased if Oracle decided to rework the code and submit it to the kernel. A lot of my work would disappear if the authors of API changes had to fix the breakage of the VB drivers. Larry