Re: 💥 PANICKED: Test report for kernel 5.10.0-rc1 (arm-next)

From: Will Deacon <will@kernel.org>
To: Rachel Sibley <rasibley@redhat.com>
Cc: catalin.marinas@arm.com, Jeff Bastian <jbastian@redhat.com>,
	linux-arm-kernel@lists.infradead.org,
	CKI Project <cki-project@redhat.com>
Subject: Re: 💥 PANICKED: Test report for kernel 5.10.0-rc1 (arm-next)
Date: Tue, 27 Oct 2020 09:19:58 +0000	[thread overview]
Message-ID: <20201027091957.GA26019@willie-the-truck> (raw)
In-Reply-To: <fb1600fc-01ae-07ec-0571-3a812268be85@redhat.com>

On Mon, Oct 26, 2020 at 06:17:03PM -0400, Rachel Sibley wrote:
> On 10/26/20 4:49 PM, Will Deacon wrote:
> > On Mon, Oct 26, 2020 at 07:42:26PM -0000, CKI Project wrote:
> > > We ran automated tests on a recent commit from this kernel tree:
> > > 
> > >         Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> > >              Commit: 3650b228f83a - Linux 5.10-rc1
> > > 
> > > The results of these automated tests are provided below.
> > > 
> > >      Overall result: FAILED (see details below)
> > >               Merge: OK
> > >             Compile: OK
> > >               Tests: PANICKED
> > > 
> > > All kernel binaries, config files, and logs are available for download here:
> > > 
> > >    https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2020/10/26/615908
> > > 
> > > One or more kernel tests failed:
> > > 
> > >      aarch64:
> > >       💥 stress: stress-ng
> > 
> > Hmm, I can't see a kernel panic in any of the logs, but I might be looking
> > in the wrong place. Please can you point me to the panic message?
> 
> You can find it in the console.log. It was triggered by stress-ng, it's also present on mainline and other
> upstream trees for both aarch64/x86_64 arches, we are working on reporting and masking the stressor.
> 
> https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2020/10/26/615908/build_aarch64_redhat%3A1003829/tests/8971427_aarch64_2_console.log
> 
> [ 9602.788234] Call trace:
> [ 9602.788243]  percpu_ref_get_many.constprop.0+0x10/0x78
> [ 9602.788246]  refill_obj_stock+0x64/0xd8
> [ 9602.788250]  obj_cgroup_uncharge+0x18/0x28
> [ 9602.788257]  memcg_slab_free_hook+0xf4/0x240
> [ 9602.788263]  kfree+0xe8/0x298
> [ 9602.788267]  proc_sys_call_handler+0x180/0x220
> [ 9602.788271]  proc_sys_read+0x1c/0x28
> [ 9602.788274]  new_sync_read+0xdc/0x158
> [ 9602.789461]  vfs_read+0x150/0x1e0
> [ 9602.789466]  ksys_read+0x60/0xe8
> [ 9602.789469]  __arm64_sys_read+0x24/0x30
> [ 9602.789472]  el0_svc_common.constprop.0+0x84/0x1b8
> [ 9602.790666]  do_el0_svc+0x2c/0x98
> [ 9602.790673]  el0_sync_handler+0xb0/0xb8
> [ 9602.790681]  el0_sync+0x178/0x180
> [ 9602.790688] Code: d503233f a9be7bfd aa0003e1 910003fd (f9400000)
> [ 9602.790691] ---[ end trace b214fef13c27568f ]---
> [ 9602.797750] usercopy: Kernel memory exposure attempt detected from SLUB object 'kmalloc-128' (offset 49, size 108)!
> [ 9603.823095] ------------[ cut here ]------------
> [ 9603.823100] kernel BUG at mm/usercopy.c:99!
> [ 9603.823111] Internal error: Oops - BUG: 0 [#4] SMP

Aha, thanks. I was grepping for "panic"!

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel