From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Alexander Potapenko <glider@google.com>
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 14:43:38 +0530 [thread overview]
Message-ID: <CA+G9fYvepJ2QVw4Fw1Bab=UOvG7PPeWMC5bjban_tSQJaVusTw@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYv7_SkA8CnMakf7nLaOTHmsf9zcbHoNT2K1_zzDtkJeyg@mail.gmail.com>
Hi Alexander,
On Mon, 24 Jul 2023 at 17:40, 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
>
> >
> > > > This crash is not easily reproducible.
> >
> > CONFIG_KFENCE_SAMPLE_INTERVAL=10
> > CONFIG_KFENCE_NUM_OBJECTS=2048
> >
> > might improve reproducibility.
>
> The above test have following Kconfigs enabled.
>
> CONFIG_HAVE_ARCH_KASAN=y
> CONFIG_HAVE_ARCH_KASAN_SW_TAGS=y
> CONFIG_HAVE_ARCH_KASAN_HW_TAGS=y
> CONFIG_HAVE_ARCH_KASAN_VMALLOC=y
> CONFIG_CC_HAS_KASAN_GENERIC=y
> CONFIG_CC_HAS_KASAN_SW_TAGS=y
> CONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=y
> # CONFIG_KASAN is not set
> CONFIG_HAVE_ARCH_KFENCE=y
> CONFIG_KFENCE=y
> CONFIG_KFENCE_SAMPLE_INTERVAL=100
> CONFIG_KFENCE_NUM_OBJECTS=255
> # CONFIG_KFENCE_DEFERRABLE is not set
> CONFIG_KFENCE_STRESS_TEST_FAULTS=0
>
> >
> > > >
> > > > 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
> >
> > It would be interesting to see the contents of
> > /sys/kernel/debug/kfence/objects together with the object address.
> > Would it be possible to boot the kernel with no_hash_pointers and add
> > a line printing the object address:
> >
> > diff --git a/mm/kfence/core.c b/mm/kfence/core.c
> > index dad3c0eb70a01..23f27f6cb18cf 100644
> > --- a/mm/kfence/core.c
> > +++ b/mm/kfence/core.c
> > @@ -1094,7 +1094,10 @@ void __kfence_free(void *addr)
> > struct kfence_metadata *meta = addr_to_metadata((unsigned long)addr);
> >
> > #ifdef CONFIG_MEMCG
> > - KFENCE_WARN_ON(meta->objcg);
> > + if (meta->objcg) {
> > + pr_err("ADDR: %px\n", addr);
> > + KFENCE_WARN_ON(1);
> > + }
> > #endif
> > /*
> > * If the objects of the cache are SLAB_TYPESAFE_BY_RCU, defer freeing
> >
> > , and then dump /sys/kernel/debug/kfence/objects?
> >
>
> This testing is running on CI loops and however, I will try to reproduce
> this locally.
I have applied the above debug patch and tested in a loop but the issues
did not reproduce yet.
- Naresh
next prev parent reply other threads:[~2023-07-25 9:13 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 [this message]
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='CA+G9fYvepJ2QVw4Fw1Bab=UOvG7PPeWMC5bjban_tSQJaVusTw@mail.gmail.com' \
--to=naresh.kamboju@linaro.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=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