On Tue, Jun 11, 2024 at 9:49 PM kernel test robot <oliver.sang@xxxxxxxxx> 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@xxxxxxxxx>
> | Closes: https://lore.kernel.org/oe-lkp/202406121026.579593f2-oliver.sang@xxxxxxxxx
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@xxxxxxxxxx/
