[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201119235042.mefu5pzrggwtzab4@kafai-mbp.dhcp.thefacebook.com>
Date: Thu, 19 Nov 2020 15:50:42 -0800
From: Martin KaFai Lau <kafai@...com>
To: Florent Revest <revest@...omium.org>
CC: <bpf@...r.kernel.org>, <viro@...iv.linux.org.uk>,
<davem@...emloft.net>, <kuba@...nel.org>, <ast@...nel.org>,
<daniel@...earbox.net>, <yhs@...com>, <andrii@...nel.org>,
<kpsingh@...omium.org>, <revest@...gle.com>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 3/5] bpf: Expose bpf_sk_storage_* to iterator programs
On Thu, Nov 19, 2020 at 05:26:52PM +0100, Florent Revest wrote:
> From: Florent Revest <revest@...gle.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.
I cannot see any hole to iter the bpf_sk_storage_map and also
bpf_sk_storage_get/delete() itself for now.
I have looked at other iters (e.g. tcp, udp, and sock_map iter).
It will be good if you can double check them also.
I think at least one more test on the tcp iter is needed.
Other than that,
Acked-by: Martin KaFai Lau <kafai@...com>
Powered by blists - more mailing lists