On Sun 18-09-16 10:26:10, zhongjiang wrote:
> From: zhong jiang <zhongjiang@xxxxxxxxxx>
>
> I hit the following issue when run a OOM case of the LTP and
> ksm enable.
>
> Call trace:
> [<ffffffc000086a88>] __switch_to+0x74/0x8c
> [<ffffffc000a1bae0>] __schedule+0x23c/0x7bc
> [<ffffffc000a1c09c>] schedule+0x3c/0x94
> [<ffffffc000a1eb84>] rwsem_down_write_failed+0x214/0x350
> [<ffffffc000a1e32c>] down_write+0x64/0x80
> [<ffffffc00021f794>] __ksm_exit+0x90/0x19c
> [<ffffffc0000be650>] mmput+0x118/0x11c
> [<ffffffc0000c3ec4>] do_exit+0x2dc/0xa74
> [<ffffffc0000c46f8>] do_group_exit+0x4c/0xe4
> [<ffffffc0000d0f34>] get_signal+0x444/0x5e0
> [<ffffffc000089fcc>] do_signal+0x1d8/0x450
> [<ffffffc00008a35c>] do_notify_resume+0x70/0x78
>
> it will leads to a hung task because the exiting task cannot get the
> mmap sem for write. but the root cause is that the ksmd holds it for
> read while allocateing memory which just takes ages to complete.
> and ksmd will loop in the following path.
>
> scan_get_next_rmap_item
> down_read
> get_next_rmap_item
> alloc_rmap_item #ksmd will loop permanently.
>
> we fix it by changing the GFP to allow the allocation sometimes fail, and
> we're not at all interested in hearing abot that.
Two things. As Tetsuo (who is not on the CC list - added) pointed out
earlier it is important to mention which kernel version this was
triggered because the current version shouldn't be affected because of
the recent oom changes (mainly the oom reaper). The other thing is that
the changelog doesn't say _why_ failing early is OK. __GFP_NORETRY not
only allows allocations to fail it also doesn't trigger OOM killer. This
sounds OK but the changelog should be clear this is intentional and
reasonable (especially when it is marked for stable).
> CC: <stable@xxxxxxxxxxxxxxx>
> Suggested-by: Hugh Dickins <hughd@xxxxxxxxxx>
> Suggested-by: Michal Hocko <mhocko@xxxxxxx>
> Signed-off-by: zhong jiang <zhongjiang@xxxxxxxxxx>
> ---
> mm/ksm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/ksm.c b/mm/ksm.c
> index 73d43ba..5048083 100644
> --- a/mm/ksm.c
> +++ b/mm/ksm.c
> @@ -283,7 +283,8 @@ static inline struct rmap_item *alloc_rmap_item(void)
> {
> struct rmap_item *rmap_item;
>
> - rmap_item = kmem_cache_zalloc(rmap_item_cache, GFP_KERNEL);
> + rmap_item = kmem_cache_zalloc(rmap_item_cache, GFP_KERNEL |
> + __GFP_NORETRY | __GFP_NOWARN);
> if (rmap_item)
> ksm_rmap_items++;
> return rmap_item;
> --
> 1.8.3.1
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>