On Sat, 29 Jun 2019 11:04:54 -0700, Song Liu wrote: > > Maybe use "__always_inline" as most other tests do? > > I meant "static __always_inline". Sure, I can do that. It doesn't seem to be as consistent as you suggest, though. There are three different forms used in selftests/bpf/progs: static __always_inline static inline __attribute__((__always_inline__)) static inline __attribute__((always_inline)) As this is a bug causing selftests to fail (at least for some clang/llvm versions), how about applying this to bpf.git as a minimal fix and unifying the progs in bpf-next? Thanks, Jiri
