Reply to post: Re: I was about to

FreeBSD 13.0 to ship without WireGuard support as dev steps in to fix 'grave issues' with initial implementation

Phil O'Sophical Silver badge

Re: I was about to

You're conflating "things that are hard to do in a kernel" and "things that C doesn't do well".

Any good kernel implementation will have kernel memory allocation/free functions that are safe to use, and just because a concept has been added to a new language to hide such mechanisms doesn't necessarily mean it's usable in kernel mode. If the designers of the language support system chose to provide a kernel-safe implementation of the feature, you can use it, but not otherwise. The same applies to any language, including C.

Kernel code, by its nature, often needs to directly access hardware and/or exact memory locations. The kind of languages that are designed to hold the programmers hand and hide such hardware features tend to make that difficult, and have to provide "special" features to bypass their inherent protections. Those can also create problems when used incorrectly.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon