On Sat, Feb 15, 2026 Alexei Starovoitov <[email protected]> wrote: > Clearly a user space issue. > The kernel side never promised to keep max_entries constant.
Thank you for the review, Alexei. I agree that callers who create maps can track their own values. However, BPF maps can be pinned to bpffs and opened by a different process that didn't create them. In that case, the consumer has no way to distinguish a kernel-adjusted max_entries from the original request. The kernel is the only entity that knows the adjustment happened. That said, I understand this may not be a strong enough use case to justify a permanent UAPI addition. Happy to drop the patch if that's the consensus. Thanks, Anand
