From: Roman Gushchin <guro@fb.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shakeel Butt <shakeelb@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>, Rik van Riel <riel@surriel.com>,
Christoph Lameter <cl@linux.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"lkp@01.org" <lkp@01.org>
Subject: Re: [mm] e52271917f: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h
Date: Thu, 23 May 2019 21:00:46 +0000 [thread overview]
Message-ID: <20190523210040.GA8420@tower.DHCP.thefacebook.com> (raw)
In-Reply-To: <20190523005858.GJ19312@shao2-debian>
On Thu, May 23, 2019 at 08:58:58AM +0800, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: e52271917f9f5159c791eda8ba748a66d659c27e ("[PATCH v4 5/7] mm: rework non-root kmem_cache lifecycle management")
> url: https://github.com/0day-ci/linux/commits/Roman-Gushchin/mm-reparent-slab-memory-on-cgroup-removal/20190517-173841
>
>
> in testcase: nvml
> with following parameters:
>
> group: obj
> test: non-pmem
>
>
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +------------------------------------------------------------------------------+------------+------------+
> | | ff756a15f3 | e52271917f |
> +------------------------------------------------------------------------------+------------+------------+
> | boot_successes | 5 | 4 |
> | boot_failures | 861 | 852 |
> | BUG:kernel_reboot-without-warning_in_test_stage | 738 | 163 |
> | BUG:kernel_hang_in_boot_stage | 120 | 122 |
> | BUG:soft_lockup-CPU##stuck_for#s | 4 | 1 |
> | RIP:free_unref_page | 1 | |
> | Kernel_panic-not_syncing:softlockup:hung_tasks | 4 | 1 |
> | RIP:free_reserved_area | 3 | 1 |
> | BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h | 0 | 560 |
> | BUG:scheduling_while_atomic | 0 | 561 |
> | WARNING:at_lib/usercopy.c:#_copy_to_user | 0 | 116 |
> | RIP:_copy_to_user | 0 | 116 |
> | WARNING:at_arch/x86/kernel/fpu/signal.c:#copy_fpstate_to_sigframe | 0 | 534 |
> | RIP:copy_fpstate_to_sigframe | 0 | 532 |
> | WARNING:at_arch/x86/kernel/signal.c:#do_signal | 0 | 527 |
> | RIP:do_signal | 0 | 526 |
> | WARNING:at_lib/usercopy.c:#_copy_from_user | 0 | 389 |
> | RIP:_copy_from_user | 0 | 388 |
> | kernel_BUG_at_mm/vmalloc.c | 0 | 304 |
> | invalid_opcode:#[##] | 0 | 304 |
> | RIP:__get_vm_area_node | 0 | 301 |
> | Kernel_panic-not_syncing:Fatal_exception_in_interrupt | 0 | 294 |
> | Kernel_panic-not_syncing:Aiee,killing_interrupt_handler | 0 | 155 |
> | WARNING:at_fs/read_write.c:#vfs_write | 0 | 15 |
> | RIP:vfs_write | 0 | 15 |
> | BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c | 0 | 101 |
> | BUG:sleeping_function_called_from_invalid_context_at_include/linux/uaccess.h | 0 | 54 |
> | Kernel_panic-not_syncing:Attempted_to_kill_init!exitcode= | 0 | 47 |
> | BUG:sleeping_function_called_from_invalid_context_at_lib/iov_iter.c | 0 | 1 |
> | BUG:sleeping_function_called_from_invalid_context_at_fs/dcache.c | 0 | 57 |
> | BUG:sleeping_function_called_from_invalid_context_at_mm/memory.c | 0 | 1 |
> | BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/mutex.c | 0 | 104 |
> | BUG:kernel_hang_in_test_stage | 0 | 5 |
> | WARNING:at_arch/x86/include/asm/uaccess.h:#strncpy_from_user | 0 | 4 |
> | RIP:strncpy_from_user | 0 | 4 |
> | WARNING:at_fs/read_write.c:#vfs_read | 0 | 4 |
> | RIP:vfs_read | 0 | 4 |
> | BUG:sleeping_function_called_from_invalid_context_at_mm/filemap.c | 0 | 3 |
> | BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c | 0 | 8 |
> | BUG:sleeping_function_called_from_invalid_context_at_mm/gup.c | 0 | 1 |
> | BUG:sleeping_function_called_from_invalid_context_at_include/linux/freezer.h | 0 | 1 |
> | BUG:sleeping_function_called_from_invalid_context_at/kb | 0 | 1 |
> +------------------------------------------------------------------------------+------------+------------+
>
>
> If you fix the issue, kindly add following tag
> Reported-by: kernel test robot <rong.a.chen@intel.com>
Hi!
It seems that it's caused by unbalanced rcu_read_lock(),
which already has been fixed in v5.
Thanks!
next prev parent reply other threads:[~2019-05-23 21:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 21:39 [PATCH v4 0/7] mm: reparent slab memory on cgroup removal Roman Gushchin
2019-05-14 21:39 ` [PATCH v4 1/7] mm: postpone kmem_cache memcg pointer initialization to memcg_link_cache() Roman Gushchin
2019-05-14 21:39 ` [PATCH v4 2/7] mm: generalize postponed non-root kmem_cache deactivation Roman Gushchin
2019-05-14 21:39 ` [PATCH v4 3/7] mm: introduce __memcg_kmem_uncharge_memcg() Roman Gushchin
2019-05-14 21:39 ` [PATCH v4 4/7] mm: unify SLAB and SLUB page accounting Roman Gushchin
2019-05-14 21:39 ` [PATCH v4 5/7] mm: rework non-root kmem_cache lifecycle management Roman Gushchin
2019-05-15 0:06 ` Shakeel Butt
2019-05-20 14:54 ` Waiman Long
2019-05-20 17:56 ` Roman Gushchin
2019-05-21 18:39 ` Waiman Long
2019-05-21 19:23 ` Roman Gushchin
2019-05-21 19:35 ` Waiman Long
2019-05-15 14:00 ` Christopher Lameter
2019-05-15 14:11 ` Shakeel Butt
2019-05-23 0:58 ` [mm] e52271917f: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2019-05-23 21:00 ` Roman Gushchin [this message]
2019-05-14 21:39 ` [PATCH v4 6/7] mm: reparent slab memory on cgroup removal Roman Gushchin
2019-05-15 0:10 ` Shakeel Butt
2019-05-14 21:39 ` [PATCH v4 7/7] mm: fix /proc/kpagecgroup interface for slab pages Roman Gushchin
2019-05-15 0:16 ` Shakeel Butt
2019-06-05 7:39 ` [PATCH v4 0/7] mm: reparent slab memory on cgroup removal Greg Thelen
2019-06-05 17:33 ` Roman Gushchin
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=20190523210040.GA8420@tower.DHCP.thefacebook.com \
--to=guro@fb.com \
--cc=Kernel-team@fb.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=mhocko@kernel.org \
--cc=riel@surriel.com \
--cc=rong.a.chen@intel.com \
--cc=shakeelb@google.com \
--cc=vdavydov.dev@gmail.com \
/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