Jakub Sitnicki wrote: > We have seen a few syzkaller reports of locking violations triggered by > map_delete from sockmap/sockhash from an unexpected code path, for instance > when irqs were disabled, or during a kfree inside a map_update. > > The consensus is [1] to block map_delete op in the verifier for programs > which are not allowed to update sockmap/sockhash already today, instead of > trying to make sockmap deletes lock-safe in every possible context. +1 thanks Jakub. This makes sense to me I've never found a use case for deleting socks from a tracing program.
