On Tue, Jan 29, 2019 at 08:04:55PM -0800, Alexei Starovoitov wrote: > > It has been explained that is a false positive here: > https://lkml.org/lkml/2018/7/25/756
Please, no external references like that. The best option is to fully include the explanation here so that a future software archeology student (note, this might be yourself in a years time) can find all relevant information in the git history. Or, if you _really_ _really_ have to refer to external sources, use: https://lkml.kernel.org/r/${msg_id} which is a controlled URL and can be made to point to any archive (currently, and sadly, lore.kernel.org). Also, since it includes the whole msg_id, people can trivially find the email in their local archive. While I agree that lkml.org is a _MUCH_ saner interface than lore (which causes eye and brain cancer for just looking at it), it is a _really_ flaky website and the url contains no clues for finding it in the local archive. > Recap: > - stackmap uses pcpu_freelist > - The lock in pcpu_freelist is a percpu lock > - stackmap is only used by tracing bpf_prog > - A tracing bpf_prog cannot be run if another bpf_prog > has already been running (ensured by the percpu bpf_prog_active counter).
