mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hritik Vijay <hritikxx8@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: "Michal Suchánek" <msuchanek@suse.de>, bpf <bpf@vger.kernel.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Martin KaFai Lau" <kafai@fb.com>,
	"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"KP Singh" <kpsingh@kernel.org>,
	Networking <netdev@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>,
	"Jiri Olsa" <jolsa@kernel.org>
Subject: Re: BPF: failed module verification on linux-next
Date: Sun, 23 May 2021 01:12:18 +0530	[thread overview]
Message-ID: <YKlemjCagqtru8i0@Journey.localdomain> (raw)
In-Reply-To: <CAEf4BzZuU2TYMapSy7s3=D8iYtVw_N+=hh2ZMGG9w6N0G1HvbA@mail.gmail.com>

On Thu, May 20, 2021 at 10:31:18PM -0700, Andrii Nakryiko wrote:
> It took me a while to reliably bisect this, but it clearly points to
> this commit:
> 
> e481fac7d80b ("mm/page_alloc: convert per-cpu list protection to local_lock")
> 
> One commit before it, 676535512684 ("mm/page_alloc: split per cpu page
> lists and zone stats -fix"), works just fine.

Thank you for pointing this out. I'm facing the same issue.
I've posted my logs in the following thread
https://lore.kernel.org/linux-next/52f77a79-5042-eca7-f80e-657ac1c515de@infradead.org/T/#t

Hrtk

  reply	other threads:[~2021-05-22 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 14:19 Michal Suchánek
2021-05-21  5:31 ` Andrii Nakryiko
2021-05-22 19:42   ` Hritik Vijay [this message]
2021-05-23 23:45   ` Hritik Vijay
2021-05-24 22:58   ` Andrii Nakryiko
2021-05-24 23:46     ` Andrii Nakryiko
2021-05-25 13:51     ` Mel Gorman
2021-05-25 19:26       ` Andrii Nakryiko
2021-05-26  8:15         ` Mel Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YKlemjCagqtru8i0@Journey.localdomain \
    --to=hritikxx8@gmail.com \
    --cc=acme@redhat.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msuchanek@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®