LWN: Comments on "More flexible memory access for BPF programs" https://lwn.net/Articles/910873/ This is a special feed containing comments posted to the individual LWN article titled "More flexible memory access for BPF programs". en-us Tue, 30 Sep 2025 23:32:48 +0000 Tue, 30 Sep 2025 23:32:48 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net More flexible memory access for BPF programs https://lwn.net/Articles/915872/ https://lwn.net/Articles/915872/ polyp <div class="FormattedComment"> All this work to the BPF mechanism makes me think about the famous Tanenbaum-Torvalds debate. Where do we have an environment where pointer accesses are checked and memory corruption is prevented outside of the sandbox where the program executes? In user-space. Perhaps a micro-kernel with user-space drivers/helpers is the better model.<br> </div> Thu, 24 Nov 2022 10:19:19 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912095/ https://lwn.net/Articles/912095/ Manifault <div class="FormattedComment"> Not sure I'm quite following how that's relevant to dynptrs, which are more about ensuring safe accesses to variably sized memory regions, rather than ensuring the lifetime of the memory it points to (though the verifier does guarantee the memory is still valid when it's accessed as well).<br> <p> For what it's worth, BPF also does support ownership and object lifetime / reference counting. kfuncs can be "acquire" and "release" kfuncs, and maps can store pointers to kernel objects. See [0] and [1] for more information.<br> <p> [0]: <a href="https://lwn.net/Articles/856005/">https://lwn.net/Articles/856005/</a><br> [1]: <a href="https://lwn.net/Articles/900749/">https://lwn.net/Articles/900749/</a><br> </div> Sun, 23 Oct 2022 20:31:50 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912082/ https://lwn.net/Articles/912082/ jhoblitt <div class="FormattedComment"> Wow! I missed the memo on that.<br> </div> Sun, 23 Oct 2022 03:05:42 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912077/ https://lwn.net/Articles/912077/ danobi <div class="FormattedComment"> I think that already exists — see CONFIG_BPF_PRELOAD. <br> </div> Sun, 23 Oct 2022 01:43:26 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912070/ https://lwn.net/Articles/912070/ amarao <div class="FormattedComment"> If only kernel had had the notion of ownership and lifetimes for variables... <br> </div> Sat, 22 Oct 2022 22:03:58 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912046/ https://lwn.net/Articles/912046/ jhoblitt <div class="FormattedComment"> It could fit that definition. Although, I think of a unikernel as taking more traditional protected memory proccess and stuffing them into kernel space.<br> <p> One could image a high performance packet molester based completely on BPF+XDP.<br> </div> Sat, 22 Oct 2022 12:17:53 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912044/ https://lwn.net/Articles/912044/ jorgegv <div class="FormattedComment"> You mean Unikernels?<br> </div> Sat, 22 Oct 2022 10:58:47 +0000 More flexible memory access for BPF programs https://lwn.net/Articles/912037/ https://lwn.net/Articles/912037/ jhoblitt <div class="FormattedComment"> If we could bundle bpf programs into the kernel image, soon we would be able boot systems and not need a userland at all. ;)<br> </div> Sat, 22 Oct 2022 00:40:22 +0000