/explore
|
You are here 
|
cocomelonc.github.io | ||
| | | | |
blog.trailofbits.com
|
|
| | | | | By Alan Cao If you love exploit mitigations, you may have heard of a new system call named mseal landing into the Linux kernel's 6.10 release, providing a protection called "memory sealing." Beyond notes from the authors, very little information about this mitigation exists. In this blog post, we'll explain what this syscall is, including... | |
| | | | |
mazzo.li
|
|
| | | | | Let's say that you have a program which relies on huge pages for performance. I couldn't find a resource fully explaining how to allocate huge pages at runtime, making sure that the huge page allocation was successful, so here it is. | |
| | | | |
niemczuk.tech
|
|
| | | | | Everyone should be familiar with the concept of brute forcing. In short it is an action of trying every possible combination till succeeding. Most often used in password hacking / hash guessing. | |
| | | | |
kstefanj.github.io
|
|
| | | I've recently spent a lot of time in memory reservation code of the JVM. It started out because we got an external contribution to enable use of multiple large page sizes for Linux. To do this in a good way some other things had to be refactored first. While taking this trip down memory lane I realized that doing a short summary of how large pages are used by the JVM might be an interesting read. | ||
