[PATCH bpf-next 2/4] bpf: Implement bpf_local_storage for inodes
kpsingh at chromium.org
Wed May 27 12:38:40 UTC 2020
On 26-May 22:08, Christoph Hellwig wrote:
> On Tue, May 26, 2020 at 06:33:34PM +0200, KP Singh wrote:
> > From: KP Singh <kpsingh at google.com>
> > Similar to bpf_local_storage for sockets, add local storage for inodes.
> > The life-cycle of storage is managed with the life-cycle of the inode.
> > i.e. the storage is destroyed along with the owning inode.
> > Since, the intention is to use this in LSM programs, the destruction is
> > done after security_inode_free in __destroy_inode.
> NAK onbloating the inode structure. Please find an out of line way
> to store your information.
The other alternative is to use lbs_inode (security blobs) and we can
do this without adding fields to struct inode.
Here is a rough diff (only illustrative, won't apply cleanly) of the
changes needed to this patch:
Once tracing has gets a whitelist based access to inode storage, I
guess it, too, can use bpf_local_storage for inodes if CONFIG_BPF_LSM
is enabled. Does this sound reasonable to the BPF folks?
More information about the Linux-security-module-archive