All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Vijay Balakrishna <vijayb@linux.microsoft.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [v3 2/2] mm: khugepaged: avoid overriding min_free_kbytes set by user
Date: Mon, 21 Sep 2020 12:54:54 +0000	[thread overview]
Message-ID: <20200921125455.0D5A12193E@mail.kernel.org> (raw)
In-Reply-To: <1600305709-2319-3-git-send-email-vijayb@linux.microsoft.com>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.8.10, v5.4.66, v4.19.146, v4.14.198, v4.9.236, v4.4.236.

v5.8.10: Build OK!
v5.4.66: Build OK!
v4.19.146: Failed to apply! Possible dependencies:
    1c30844d2dfe ("mm: reclaim small amounts of memory when an external fragmentation event occurs")
    24512228b7a3 ("mm: do not boost watermarks to avoid fragmentation for the DISCONTIG memory model")
    426dcd4b600f ("hexagon: switch to NO_BOOTMEM")
    6471f52af786 ("alpha: switch to NO_BOOTMEM")
    6bb154504f8b ("mm, page_alloc: spread allocations across zones before introducing fragmentation")
    9705bea5f833 ("mm: convert zone->managed_pages to atomic variable")
    a921444382b4 ("mm: move zone watermark accesses behind an accessor")
    b4a991ec584b ("mm: remove CONFIG_NO_BOOTMEM")
    bc3ec75de545 ("dma-mapping: merge direct and noncoherent ops")
    bda49a81164a ("mm: remove nobootmem")
    c32e64e852f3 ("csky: Build infrastructure")
    e0a9317d9004 ("hexagon: use generic dma_noncoherent_ops")
    f406f222d4b2 ("hexagon: implement the sync_sg_for_device DMA operation")

v4.14.198: Failed to apply! Possible dependencies:
    1c30844d2dfe ("mm: reclaim small amounts of memory when an external fragmentation event occurs")
    1d47a3ec09b5 ("mm/cma: remove ALLOC_CMA")
    24512228b7a3 ("mm: do not boost watermarks to avoid fragmentation for the DISCONTIG memory model")
    3d2054ad8c2d ("ARM: CMA: avoid double mapping to the CMA area if CONFIG_HIGHMEM=y")
    453f85d43fa9 ("mm: remove __GFP_COLD")
    6bb154504f8b ("mm, page_alloc: spread allocations across zones before introducing fragmentation")
    85ccc8fa81af ("mm/page_alloc: make sure __rmqueue() etc are always inline")
    a921444382b4 ("mm: move zone watermark accesses behind an accessor")
    bad8c6c0b114 ("mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE")

v4.9.236: Failed to apply! Possible dependencies:
    14b468791fa9 ("mm: workingset: move shadow entry tracking to radix tree exceptional tracking")
    1c30844d2dfe ("mm: reclaim small amounts of memory when an external fragmentation event occurs")
    24512228b7a3 ("mm: do not boost watermarks to avoid fragmentation for the DISCONTIG memory model")
    2a2e48854d70 ("mm: vmscan: fix IO/refault regression in cache workingset transition")
    31176c781508 ("mm: memcontrol: clean up memory.events counting function")
    6bb154504f8b ("mm, page_alloc: spread allocations across zones before introducing fragmentation")
    8e675f7af507 ("mm/oom_kill: count global and memory cgroup oom kills")
    9d998b4f1e39 ("mm, vmscan: add active list aging tracepoint")
    a921444382b4 ("mm: move zone watermark accesses behind an accessor")
    cd04ae1e2dc8 ("mm, oom: do not rely on TIF_MEMDIE for memory reserves access")
    d6622f6365db ("mm/vmscan: more restrictive condition for retry in do_try_to_free_pages")
    dcec0b60a821 ("mm, vmscan: add mm_vmscan_inactive_list_is_low tracepoint")
    df0e53d0619e ("mm: memcontrol: re-use global VM event enum")
    f7942430e40f ("lib: radix-tree: native accounting of exceptional entries")

v4.4.236: Failed to apply! Possible dependencies:
    0b57d6ba0bd1 ("mm/mmap.c: remove redundant local variables for may_expand_vm()")
    1170532bb49f ("mm: convert printk(KERN_<LEVEL> to pr_<level>")
    5a6e75f8110c ("shmem: prepare huge= mount option and sysfs knob")
    756a025f0009 ("mm: coalesce split strings")
    84638335900f ("mm: rework virtual memory accounting")
    8cee852ec53f ("mm, procfs: breakdown RSS for anon, shmem and file in /proc/pid/status")
    b46e756f5e47 ("thp: extract khugepaged from mm/huge_memory.c")
    d07e22597d1d ("mm: mmap: add new /proc tunable for mmap_base ASLR")
    d977d56ce5b3 ("mm: warn about VmData over RLIMIT_DATA")
    d9fe4fab1197 ("x86/mm/pat: Add untrack_pfn_moved for mremap")
    eca56ff906bd ("mm, shmem: add internal shmem resident memory accounting")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

      parent reply	other threads:[~2020-09-21 12:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  1:21 [v3 0/2] recalculate min_free_kbytes post memory hotplug Vijay Balakrishna
2020-09-17  1:21 ` [v3 1/2] mm: khugepaged: recalculate min_free_kbytes after memory hotplug as expected by khugepaged Vijay Balakrishna
2020-09-21 12:55   ` Sasha Levin
2020-09-23 21:27   ` Vijay Balakrishna
2020-09-25  2:51     ` Andrew Morton
2020-09-25  7:45       ` Michal Hocko
2020-09-25  7:42   ` Michal Hocko
2020-09-25 16:31     ` Vijay Balakrishna
2020-09-17  1:21 ` [v3 2/2] mm: khugepaged: avoid overriding min_free_kbytes set by user Vijay Balakrishna
2020-09-17  4:22   ` Vijay Balakrishna
2020-09-21 12:54   ` Sasha Levin [this message]

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=20200921125455.0D5A12193E@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.