Theme 1 – “Agent” is a long‑standing, non‑AI term
- jaggederest: “Agent is an old school way to say 'constantly running daemon to accomplish some specific purpose'.”
- Brian_K_White: “An agent may or may not also be a daemon… Countless ordinary 'things that run on a host and perform tasks for some other host' were always called agents.”
- selcuka: “Agent is an older term, apparently from the 1950s… The idea of an agent originated with John McCarthy in the mid‑1950’s.”
- mrbluecoat (questioning the headline): “So you highlight 'Not AI Gen' but you call the solution 'Agent'? :D”
Theme 2 – Debate over the novelty and usefulness of memoization in eBPF
- danudey: “Very confused by the article. Is memoization new to the eBPF world? Did the author only just learn about it and wanted to use it?”
- debatem1: “Definitely not new in eBPF or LSMs in general.”
- asdfman123: “I don't know what any of these acronyms mean. With just a little more explanation the article could be accessible to a wider developer audience.”
- Allybag (on the claimed 90 % speed‑up): “Seems like the 90% faster case is opening the same exact file every single time… So you can make the headline 'Drop performance cost by 90%!' or 'Modestly increase performance cost' and be correct.”
Theme 3 – Security / correctness worries about caching path‑policy mappings
- bawolff: “Wouldn't this break if you moved a directory that is somewhere up the path? Seems like a security issue if you cache what policy applies but the policy could change by user action.”
- nathannaveen (author): “If we are protecting a directory, then only people with access will be able to move the dir… we are thinking of evicting the inode associated with the directory from the cache if a directory is moved.”
- ComputerGuru: “How do your path-only rules handle the many approaches for loading a file but making it appear to have a different path, such as bind mounts for one example?”
- yxhuvud: “And uh, what happens if the active user permission changes?”