From: Shakeel Butt <shakeelb@google.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Raghuram Thammiraju <raghuram.thammiraju@arm.com>,
Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Vasily Averin <vvs@openvz.org>,
Qian Cai <quic_qiancai@quicinc.com>
Subject: Re: [next] arm64: boot failed - next-20220606
Date: Tue, 7 Jun 2022 07:17:34 -0700 [thread overview]
Message-ID: <CALvZod72bp9ejY+KghaUGkoXDrOMMbs_ofsopGib=MY4jzhRkg@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYve1faH7AmpEa-p_ySb_WCgc4DdjqyS6fSdiJYsaEi=rA@mail.gmail.com>
On Tue, Jun 7, 2022 at 3:28 AM Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Hi Shakeel,
>
> > > > Can you test v5.19-rc1, please? If that does not fail, then you could
> > > > bisect between that and next-20220606 ...
> > > >
> > >
> > > This is already reported at
> > > https://lore.kernel.org/all/Yp4F6n2Ie32re7Ed@qian/ and I think we know
> > > the underlying issue (which is calling virt_to_page() on a vmalloc
> > > address).
> >
> > Sorry, I might be wrong. Just checked the stacktrace again and it
> > seems like the failure is happening in early boot in this report.
> > Though the error "Unable to handle kernel paging request at virtual
> > address" is happening in the function mem_cgroup_from_obj().
> >
> > Naresh, can you repro the issue if you revert the patch "net: set
> > proper memcg for net_init hooks allocations"?
>
> yes. You are right !
> 19ee3818b7c6 ("net: set proper memcg for net_init hooks allocations")
> After reverting this single commit I am able to boot arm64 successfully.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
Can you please run script/faddr2line on "mem_cgroup_from_obj+0x2c/0x120"?
next prev parent reply other threads:[~2022-06-07 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 11:46 Naresh Kamboju
2022-06-07 5:30 ` Naresh Kamboju
2022-06-07 6:25 ` Stephen Rothwell
2022-06-07 6:36 ` Shakeel Butt
2022-06-07 6:44 ` Shakeel Butt
2022-06-07 10:27 ` Naresh Kamboju
2022-06-07 14:17 ` Shakeel Butt [this message]
2022-06-07 15:29 ` Naresh Kamboju
2022-06-09 2:49 ` Vasily Averin
2022-06-09 3:44 ` Kefeng Wang
2022-06-09 4:43 ` Kefeng Wang
2022-06-09 5:19 ` Roman Gushchin
2022-06-09 10:11 ` Will Deacon
2022-06-09 10:25 ` Catalin Marinas
2022-06-09 15:23 ` Shakeel Butt
2022-06-07 10:24 ` Naresh Kamboju
2022-06-09 17:26 ` Roman Gushchin
2022-06-09 17:47 ` Shakeel Butt
2022-06-09 17:56 ` Roman Gushchin
2022-06-09 19:12 ` Shakeel Butt
2022-06-09 22:05 ` Roman Gushchin
2022-06-09 22:16 ` Shakeel Butt
2022-06-10 10:56 ` Naresh Kamboju
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='CALvZod72bp9ejY+KghaUGkoXDrOMMbs_ofsopGib=MY4jzhRkg@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=quic_qiancai@quicinc.com \
--cc=raghuram.thammiraju@arm.com \
--cc=regressions@lists.linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=vvs@openvz.org \
--cc=will@kernel.org \
/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