-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How are the knowledge-v*.json files generated? #6
Comments
Hi, Those files currently are generated manually. In most case, the knowledge is not changed. For example, 5.12 works for most 5.x versions. If you are working on latest Linux kernel and find the knowledge can not work well, you can open a issue for that and I can help when I am available. In fact, I was trying to develop a tool to automatically update those files but I have not finished the tool. |
Cool! Thanks for the reply. Currently, I am using a combination of grep on the .ll file (disassembled llvm) and weggli on the C source to check if anything is different with my target. I have found some slight differences in offsets, but more automation would be very helpful! Happy to help out and test if needed :) |
Btw,
How do you "test" this? Do you just look out the output syscall descriptors and check if they look reasonable? |
Yes. |
Hi there! Really great paper.
I wanted to understand how
config/knowledge-5.12.json
andconfig/knowledge-6.1.json
are generated. How would I make new knowledge files if I wanted to port to other kernel versions? Are these automatically generated or manually written?Any pointers would be greatly appreciated!
The text was updated successfully, but these errors were encountered: