-
Notifications
You must be signed in to change notification settings - Fork 35
Merging uksm upstream? #41
Comments
I have no plans. I think it would be a lot of work and this concept introduce security risks. That would open kernel for new vulnerabilities. |
But it would be work that leads somewhere. Just maintaining these patches outside of kernel tree is also lot of work, but it's only useful in the short run. All similar projects that maintain kernel patches outside upstream eventualy get tired and cease to maintain their codebase...
Well. That might be true. I don't fully understand how this side-chanel atack vector on samepage merging is supposed to work. But there are two concerns: 1.) Kernel already contains KSM, which probably suffers from the same problem (eg. attacking one Qemu VM from another) and nobody seems to complain... 2.) I think this is OK as long as it's disabled by default and users are warned about the risks they can face if they're going to enable it. |
I'll try to do that, but
|
If you put upstream feedback here, then we (community) could help with some issues together |
@Szpadel Thanks for kind words :) |
I will post those patches in the next merge window as they are and let's see what developers will say. |
We know that current patch is unacceptable for merge from previous attempt. We should send the patch as is at any time since during merge window there will be no time to review it. |
So there was an attempt, let me check... |
Looks like a bit of a work... i will try to do some coding, but can't promise anything since I am very short with time :( |
5.4 got some fixes to zram race conditions, maybe those issues are resolved now |
Any progress on this? |
I would love to see that integrated into the main kernel, it would benefit so many systems. Is there any status updates on that? |
On a side note, there are threads for this on Proxmox website as well: |
The problem with merging this upstream is that there's no-one who really understands the code to maintain it. IIRC, @dolohow stepped up to update the old patches, but did not write them, nor has a complete understanding of how the code works. |
Thank you guys for working on this. I'm grateful to the original authors as well. The kernel coding is a bit of black art for me.... yet this code works for me. |
Hello,
can we expect this to be merged upstream? are there some reasons why this might not be included?
The text was updated successfully, but these errors were encountered: