Request Kernel Patch - bcache

[noahmehl]

Team,

We are hitting an issue in bcache that seems to be part of the Linux Kernel that has a pending patch set:

https://lore.kernel.org/linux-bcache/20230307134852.8288-1-mingzhe.zou@easystack.cn/T/#u

However, it's not merged upstream, and even launchpad has something open for this:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040

Is it possible to add this to the PVE kernel? If not, is there a process for getting this kind of change distributed?

Thanks in advanced!

~Noah

 

[LnxBil]

The proxmox kernel (unified for all producs) is based on the Ubuntu LTS kernel so when bcache will be integrated in the Ubuntu LTS kernel, it'll be also available in PVE.

 

[noahmehl]

@LnxBil bcache has been integrated in the kernel for a long time. Does the PVE kernel have no further customizations beyond the Ubuntu LTS maintained kernels?

 

[LnxBil]

@LnxBil bcache has been integrated in the kernel for a long time. Does the PVE kernel have no further customizations beyond the Ubuntu LTS maintained kernels?

AFAIK, it's a vanilla Ubuntu LTS kernel with some patches (e.g. ZFS). Please refer to the commits.

 

[fabian]

since it seems to be on-track for being fixed/backported both in upstream stable kernels (https://lore.kernel.org/lkml/20231128210615.875085-7-sashal@kernel.org) as well as in Ubuntu (your launchpad link), it will become available in our PVE kernels as well afterwards.

 

[noahmehl]

I guess all I had to do was poke the bear...

That being said, there does seem to be a bit of custom (e.g. not fully upstream) patches going into the kernel. Is there any details on how it's decided what goes into PVE kernel?

 

[fabian]

the usual things
- cherry-picks from upstream for important bugs, and much more rarely, features
- reverts of changes that negatively affect our usage
- adapted defaults/config values for various settings
- bug fixes developed by us which are not yet included upstream
- changes related to packaging (e.g., taking the timestamp from the package changelog)

 

[noahmehl]

@fabian thank you for the detail