On Fri, Feb 22, 2019 at 11:42 PM <valdis.kletni...@vt.edu> wrote: > > On Thu, 21 Feb 2019 14:39:27 +0100, Daniel Borkmann said: > > Fyi, false positive and already fixed in bpf-next. > > > > (https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=435b3ff5b08a99a15647be32735abf8db66cea9a) > > Is there a reason this commit appeared in next-20190221 but did not seem to be > in next-20190222 (confirmed via 'git tag --contains')? > > [/usr/src/linux-next] git tag -l next-20190222 > next-20190222 > [/usr/src/linux-next] git tag --contains > 435b3ff5b08a99a15647be32735abf8db66cea9a > next-20190221 > > (I went ahead and 'git cherry-pick -n' it on top of 0222)
It was reverted by ast@, he wanted to fix it in a different way: https://lore.kernel.org/netdev/20190221192916.2mcd4fmxbdj2j...@ast-mbp.dhcp.thefacebook.com/
