linux-kernel - linux-next: manual merge of the akpm-current tree with the jc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20191002131835.51809ea9@canb.auug.org.au>
Date:   Wed, 2 Oct 2019 13:18:35 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Jonathan Corbet <corbet@....net>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jon Haslam <jonhaslam@...com>,
        Chris Down <chris@...isdown.name>
Subject: linux-next: manual merge of the akpm-current tree with the jc_docs
 tree

Hi all,

Today's linux-next merge of the akpm-current tree got a conflict in:

  Documentation/admin-guide/cgroup-v2.rst

between commit:

  6ee0fac199e1 ("docs: fix memory.low description in cgroup-v2.rst")

from the jc_docs tree and commit:

  3968bb6dec48 ("mm, memcg: proportional memory.{low,min} reclaim")

from the akpm-current tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc Documentation/admin-guide/cgroup-v2.rst
index 26d1cde6b34a,5361ebec3361..000000000000
--- a/Documentation/admin-guide/cgroup-v2.rst
+++ b/Documentation/admin-guide/cgroup-v2.rst
@@@ -1117,8 -1120,11 +1120,11 @@@ PAGE_SIZE multiple when read back
  
  	Best-effort memory protection.  If the memory usage of a
  	cgroup is within its effective low boundary, the cgroup's
 -	memory won't be reclaimed unless memory can be reclaimed
 -	from unprotected cgroups.  Above the effective low boundary (or
 -	effective min boundary if it is higher), pages are reclaimed
 -	proportionally to the overage, reducing reclaim pressure for
 -	smaller overages.
 +	memory won't be reclaimed unless there is no reclaimable
- 	memory available in unprotected cgroups.
++	memory available in unprotected cgroups.  Above the effective
++	low boundary (or effective min boundary if it is higher), pages
++	are reclaimed proportionally to the overage, reducing reclaim
++	pressure for smaller overages.
  
  	Effective low boundary is limited by memory.low values of
  	all ancestor cgroups. If there is memory.low overcommitment

Content of type "application/pgp-signature" skipped