lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14415.1550875312@turing-police.cc.vt.edu>
Date:   Fri, 22 Feb 2019 17:41:52 -0500
From:   valdis.kletnieks@...edu
To:     Daniel Borkmann <daniel@...earbox.net>
cc:     kernel test robot <lkp@...el.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Jann Horn <jannh@...gle.com>,
        Alexei Starovoitov <ast@...nel.org>,
        Song Liu <songliubraving@...com>,
        LKML <linux-kernel@...r.kernel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>, lkp@...org
Subject: Re: [bpf] 568f196756: BUG:assuming_atomic_context_at_kernel/seccomp.c

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)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ