From: Linus Torvalds <torvalds@linux-foundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Muchun Song <muchun.song@linux.dev>,
Alexander Potapenko <glider@google.com>
Cc: 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: Sat, 22 Jul 2023 09:36:57 -0700 [thread overview]
Message-ID: <CAHk-=wh1kqn2qAAkQb85_SCwn_mWKC3F51E0phJaf=4+pTt0cg@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYvgy22wiY=c3wLOrCM6o33636abhtEynXhJkqxJh4ca0A@mail.gmail.com>
[ 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
On Sat, 22 Jul 2023 at 01:06, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Results from Linaro’s test farm.
> No regressions on arm64, arm, x86_64, and i386.
>
> Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> 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
>
> This crash is not easily reproducible.
>
> boot logs:
> --------
> [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x000f0510]
> [ 0.000000] Linux version 6.4.5-rc1 (tuxmake@tuxmake)
> (aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils
> for Debian) 2.40) #1 SMP PREEMPT @1689957802
> [ 0.000000] random: crng init done
> [ 0.000000] Machine model: linux,dummy-virt
> ...
> [ 0.006821] kfence: initialized - using 33554432 bytes for 255
> objects at 0x(____ptrval____)-0x(____ptrval____)
> ...
> [ 7.726994] ------------[ cut here ]------------
> [ 7.727704] WARNING: CPU: 1 PID: 1 at mm/kfence/core.c:1097
> __kfence_free+0x84/0xc8
...
> [ 7.746478] Call trace:
> [ 7.746776] __kfence_free+0x84/0xc8
> [ 7.747134] __slab_free+0x490/0x508
> [ 7.748063] __kmem_cache_free+0x2b4/0x2d0
> [ 7.748377] kfree+0x78/0x140
> [ 7.748638] single_release+0x40/0x60
> [ 7.750664] __fput+0x78/0x260
> [ 7.751065] ____fput+0x18/0x30
> [ 7.752086] task_work_run+0x80/0xe0
> [ 7.753122] do_notify_resume+0x200/0x1398
> [ 7.754292] el0_svc+0xec/0x100
> [ 7.754573] el0t_64_sync_handler+0xf4/0x120
> [ 7.755559] el0t_64_sync+0x190/0x198
next parent reply other threads:[~2023-07-22 16:37 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 [this message]
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
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='CAHk-=wh1kqn2qAAkQb85_SCwn_mWKC3F51E0phJaf=4+pTt0cg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=roman.gushchin@linux.dev \
/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