On Sat, 23 Feb 2019 00:15:38 +0100, Jann Horn said:
> On Fri, Feb 22, 2019 at 11:42 PM wrote:
> > Is there a reason this commit appeared in next-20190221 but did not seem to
> > be
> > in next-20190222 (confirmed via 'git tag --contains')?y ast@, he wanted to
> > fix it in a different way:
> htt
On Fri, Feb 22, 2019 at 11:42 PM 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
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
On 02/21/2019 02:35 PM, kernel test robot wrote:
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 568f196756ad9fe2b49c46bbf6a9de1b190438b4 ("bpf: check that BPF
> programs run with preemption disabled")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git ma
4 matches
Mail list logo
