Conversation
Thorsten Leemhuis (acct. 1/4)
kernellogger@fosstodon.org
The new system call #mseal()[1] after multiple revisions and various discussions[2] finally made it to #linux-next and thus is slated to appear in #LinuxKernel 6.10:
https://lore.kernel.org/all/20240415163527.626541-1-jeffxu@chromium.org/T/#u
[1] "In a nutshell, mseal() protects the VMAs of a given virtual memory range against modifications, such as changes to their permission bits."
[2] https://lwn.net/Articles/948129/
1
2
1
Jarkko Sakkinen
jarkko
@kernellogger hmm... is this inspired *BSD? have a faint memory that it had something similar but could remember wrong. nice addition anyway although personally ntsync driver is the thing for me in the next release :-)
2
0
0
*BSD? yeah, see the linked lwn article for details; initially it was supposed to work slightly different, but Linus had concerns.
0
0
1
Thorsten Leemhuis (acct. 1/4)
kernellogger@fosstodon.organd ntsync: seems many people are really excited about it.
Would be kinda funny if lots of native Linux apps over time to start relying on a technique with "nt" in the name 😄
1
0
2
@kernellogger if you consider audio plugins they are actually just data processors so getting windows IO work right in Linux is the key. I don't see then actually any reason to do actual Linux ports of those plugins because with right stack underneath you could make the already existing Windows plugins perform better than in native Windows.
https://github.com/robbert-vdh/yabridge sort of solved the audio equation except for the IO part that requires better support from kernel. now we get that part right...
https://github.com/robbert-vdh/yabridge sort of solved the audio equation except for the IO part that requires better support from kernel. now we get that part right...
0
0
2