From: Alexander Potapenko <glider@google.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
Marco Elver <elver@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH 6.4 000/292] 6.4.5-rc1 review
Date: Tue, 25 Jul 2023 13:52:21 +0200 [thread overview]
Message-ID: <CAG_fn=UtVOn0s2fQX3N3zGVUHWLALxFU1UtWszJWwcvQZv-gZw@mail.gmail.com> (raw)
In-Reply-To: <CAG_fn=ULuhP_zSR0Uk-nUZs3DRmbdbyN-NZDZ3kBdG5Kgcrzyw@mail.gmail.com>
On Tue, Jul 25, 2023 at 11:59 AM Alexander Potapenko <glider@google.com> wrote:
>
> On Mon, Jul 24, 2023 at 2:10 PM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
> >
> > On Mon, 24 Jul 2023 at 15:50, Alexander Potapenko <glider@google.com> wrote:
> > >
> > > On Sat, Jul 22, 2023 at 6:37 PM Linus Torvalds
> > > <torvalds@linux-foundation.org> wrote:
> > > >
> > > > [ Removed the stable reviewers, bringing in the kfence people ]
> > > >
> > > > See
> > > >
> > > > https://lore.kernel.org/lkml/CA+G9fYvgy22wiY=c3wLOrCM6o33636abhtEynXhJkqxJh4ca0A@mail.gmail.com/
> > > >
> > > > for the original report. The warning was introduced in 8f0b36497303
> > > > ("mm: kfence: fix objcgs vector allocation"), and Google doesn't find
> > > > any other cases of this.
> > > >
> > > > Anybody?
> > > >
> > > > Linus
> > > >
> > >
> > >
> > > > > NOTE:
> > > > > The following kernel warning was noticed while booting qemu-arm64
> > > > > with these configs enabled on stable rc 6.4.5-rc1.
> > > > >
> > > > > CONFIG_ARM64_64K_PAGES=y
> > > > > CONFIG_KFENCE=y
> > >
> > > Is there a full config somewhere?
> >
> > Please find build details
> > - https://storage.tuxsuite.com/public/linaro/lkft/builds/2StEPFnEfoD076PRu8fIxjexhnM/
> > - https://storage.tuxsuite.com/public/linaro/lkft/builds/2StEPFnEfoD076PRu8fIxjexhnM/config
> > - https://storage.tuxsuite.com/public/linaro/lkft/builds/2StEPFnEfoD076PRu8fIxjexhnM/vmlinux.xz
> > - https://storage.tuxsuite.com/public/linaro/lkft/builds/2StEPFnEfoD076PRu8fIxjexhnM/System.map
> > - https://storage.tuxsuite.com/public/linaro/lkft/builds/2StEPFnEfoD076PRu8fIxjexhnM/Image.gz
>
> I am afraid it still doesn't help much.
> I installed tuxmake into a virtualenv and tried running:
Ok, my buildroot indeed lacked the BR2_ARM64_PAGE_SIZE_64K. I am now
able to boot a kernel with your config, trying to reproduce the
problem locally...
next prev parent reply other threads:[~2023-07-25 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230721160528.800311148@linuxfoundation.org>
[not found] ` <CA+G9fYvgy22wiY=c3wLOrCM6o33636abhtEynXhJkqxJh4ca0A@mail.gmail.com>
2023-07-22 16:36 ` Linus Torvalds
2023-07-24 10:19 ` Alexander Potapenko
2023-07-24 12:10 ` Naresh Kamboju
2023-07-25 9:13 ` Naresh Kamboju
2023-07-25 9:59 ` Alexander Potapenko
2023-07-25 11:52 ` Alexander Potapenko [this message]
2023-07-25 13:39 ` Naresh Kamboju
2023-07-25 16:21 ` Alexander Potapenko
2023-07-26 16:52 ` Alexander Potapenko
2023-07-27 7:02 ` Muchun Song
2023-07-27 7:26 ` Muchun Song
2023-07-25 13:36 ` 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='CAG_fn=UtVOn0s2fQX3N3zGVUHWLALxFU1UtWszJWwcvQZv-gZw@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=elver@google.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=roman.gushchin@linux.dev \
--cc=torvalds@linux-foundation.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