linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [linux-next:master] [mm]  5d4a36365b: kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail
@ 2024-06-12  4:49 kernel test robot
  2024-06-12  6:54 ` Yosry Ahmed
  0 siblings, 1 reply; 2+ messages in thread
From: kernel test robot @ 2024-06-12  4:49 UTC (permalink / raw)
  To: Yosry Ahmed
  Cc: oe-lkp, lkp, Linux Memory Management List, Andrew Morton,
	David Hildenbrand, oliver.sang



Hello,

kernel test robot noticed "kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail" on:

commit: 5d4a36365be0fc9085c192b0015b789ddfaca1f8 ("mm: rmap: abstract updating per-node and per-memcg stats")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master

[test failed on linux-next/master d35b2284e966c0bef3e2182a5c5ea02177dd32e4]

in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:

	group: cgroup



compiler: gcc-13
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (Ivy Bridge) with 16G memory

(please refer to attached dmesg/kmsg for entire log/backtrace)


bc80784601ad8fd8 5d4a36365be0fc9085c192b0015
---------------- ---------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
           :6          100%           6:6     kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail




If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202406121026.579593f2-oliver.sang@intel.com



# timeout set to 300
# selftests: cgroup: test_kmem
# not ok 1 test_kmem_basic
# memory.current = 331776
# anon + file + kernel + sock = 34463744
# anon = 34406400
# file = 0
# kernel = 57344
# sock = 0
# not ok 2 test_kmem_memcg_deletion     <-----
# ok 3 test_kmem_proc_kpagecgroup
# ok 4 test_kmem_kernel_stacks
# ok 5 test_kmem_dead_cgroups
# memory.current 20328448
# percpu 13920000
# not ok 6 test_percpu_basic
not ok 2 selftests: cgroup: test_kmem # exit=1



The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240612/202406121026.579593f2-oliver.sang@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [linux-next:master] [mm] 5d4a36365b: kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail
  2024-06-12  4:49 [linux-next:master] [mm] 5d4a36365b: kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail kernel test robot
@ 2024-06-12  6:54 ` Yosry Ahmed
  0 siblings, 0 replies; 2+ messages in thread
From: Yosry Ahmed @ 2024-06-12  6:54 UTC (permalink / raw)
  To: kernel test robot
  Cc: oe-lkp, lkp, Linux Memory Management List, Andrew Morton,
	David Hildenbrand, Hugh Dickins

On Tue, Jun 11, 2024 at 9:49 PM kernel test robot <oliver.sang@intel.com> wrote:
>
>
>
> Hello,
>
> kernel test robot noticed "kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail" on:
>
> commit: 5d4a36365be0fc9085c192b0015b789ddfaca1f8 ("mm: rmap: abstract updating per-node and per-memcg stats")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> [test failed on linux-next/master d35b2284e966c0bef3e2182a5c5ea02177dd32e4]
>
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-977d51cf-1_20240508
> with following parameters:
>
>         group: cgroup
>
>
>
> compiler: gcc-13
> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (Ivy Bridge) with 16G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
> bc80784601ad8fd8 5d4a36365be0fc9085c192b0015
> ---------------- ---------------------------
>        fail:runs  %reproduction    fail:runs
>            |             |             |
>            :6          100%           6:6     kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail
>
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <oliver.sang@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202406121026.579593f2-oliver.sang@intel.com

I believe Hugh just sent a fix for this [1]. He intends for it to be
squashed into the original patch (still in mm-unstable), so I think we
don't need Reported-by and Closes there.

[1]https://lore.kernel.org/linux-mm/49914517-dfc7-e784-fde0-0e08fafbecc2@google.com/


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-06-12  6:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-12  4:49 [linux-next:master] [mm] 5d4a36365b: kernel-selftests.cgroup.test_kmem.test_kmem_memcg_deletion.fail kernel test robot
2024-06-12  6:54 ` Yosry Ahmed

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox