Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190221133556.eqzclahgngq53s64@inn2.lkp.intel.com>
 <cdd8143b-7719-b51e-5a6a-6bdc065cc773@iogearbox.net> <14415.1550875312@turing-police.cc.vt.edu>
In-Reply-To: <14415.1550875312@turing-police.cc.vt.edu>
From:   Jann Horn <jannh@google.com>
Date:   Sat, 23 Feb 2019 00:15:38 +0100
Message-ID: <CAG48ez009feoF9=AwQ1qHSnuXeFJnAsHREmtrT-+HgPueytyCw@mail.gmail.com>
Subject: Re: [bpf] 568f196756: BUG:assuming_atomic_context_at_kernel/seccomp.c
To:     Valdis Kletnieks <valdis.kletnieks@vt.edu>
Cc:     Daniel Borkmann <daniel@iogearbox.net>,
        kernel test robot <lkp@intel.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Alexei Starovoitov <ast@kernel.org>,
        Song Liu <songliubraving@fb.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Stephen Rothwell <sfr@canb.auug.org.au>, lkp@01.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Feb 22, 2019 at 11:42 PM <valdis.kletnieks@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.2mcd4fmxbdj2j2u3@ast-mbp.dhcp.thefacebook.com/