Author here. Yes, the issues you pointed out are mostly already captured via // TODO and // FIXME comments. The library was written in about a day. I could prob

Author here. Yes, the issues you pointed out are mostly already captured via // TODO and // FIXME comments. The library was written in about a day. I could probably add the basic block length check (as it is, I just check for 0xC3), but I wasn't able to readily figure out how to disable interrupts during patching. If you have a suggestion, I'll implement it. The nice thing about a reusable library is that safety improvements can be made and shared with other clients. (As an aside, can I suggest posting an issue to GitHub? I might not have seen this thread, and xnu_override users who want to know of its shortcomings should also be able to find your comments easily.) I hope that someone who has the know-how to reverse engineer the kernel, devise a patch to add desired behavior, and write a kernel extension to implement that behavior, will understand that patching the kernel is inherently a dangerous thing to do—and will actually test that their change works. I wrote this as an alternative to other patchers which provide a string search and replace on the system kexts. Reverting these patches, dealing with the code signing fallout, and updating them for a new release are significantly more challenging with this style of patching.