On Thu, Nov 19, 2020 at 5:27 PM Florent Revest <rev...@chromium.org> wrote: > > From: Florent Revest <rev...@google.com> > > Iterators are currently used to expose kernel information to userspace > over fast procfs-like files but iterators could also be used to > manipulate local storage. For example, the task_file iterator could be > used to initialize a socket local storage with associations between > processes and sockets or to selectively delete local storage values. > > This exposes both socket local storage helpers to all iterators. > Alternatively we could expose it to only certain iterators with strcmps > on prog->aux->attach_func_name.
Since you mentioned the alternative here, maybe you can also explain why you chose the current approach.
