GitHub-Mirror/Star64_linux

mirror of https://github.com/Fishwaldo/Star64_linux.git synced 2025-03-25 16:44:38 +00:00

No description

Find a file

Yafang Shao 04fd61a4e0 mm, memcg: fix inconsistent oom event behavior A recent commit `9852ae3fe5` ("mm, memcg: consider subtrees in memory.events") changed the behavior of memcg events, which will now consider subtrees in memory.events. But oom_kill event is a special one as it is used in both cgroup1 and cgroup2. In cgroup1, it is displayed in memory.oom_control. The file memory.oom_control is in both root memcg and non root memcg, that is different with memory.event as it only in non-root memcg. That commit is okay for cgroup2, but it is not okay for cgroup1 as it will cause inconsistent behavior between root memcg and non-root memcg. Here's an example on why this behavior is inconsistent in cgroup1. root memcg / memcg foo / memcg bar Suppose there's an oom_kill in memcg bar, then the oon_kill will be root memcg : memory.oom_control(oom_kill) 0 / memcg foo : memory.oom_control(oom_kill) 1 / memcg bar : memory.oom_control(oom_kill) 1 For the non-root memcg, its memory.oom_control(oom_kill) includes its descendants' oom_kill, but for root memcg, it doesn't include its descendants' oom_kill. That means, memory.oom_control(oom_kill) has different meanings in different memcgs. That is inconsistent. Then the user has to know whether the memcg is root or not. If we can't fully support it in cgroup1, for example by adding memory.events.local into cgroup1 as well, then let's don't touch its original behavior. Fixes: `9852ae3fe5` ("mm, memcg: consider subtrees in memory.events") Reported-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Yafang Shao <laoar.shao@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Reviewed-by: Shakeel Butt <shakeelb@google.com> Acked-by: Johannes Weiner <hannes@cmpxchg.org> Acked-by: Chris Down <chris@chrisdown.name> Acked-by: Michal Hocko <mhocko@suse.com> Cc: <stable@vger.kernel.org> Link: http://lkml.kernel.org/r/20200502141055.7378-1-laoar.shao@gmail.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2020-05-14 10:00:35 -07:00
arch	A set of fixes for x86:	2020-05-10 11:59:53 -07:00
block	bdi: use bdi_dev_name() to get device name	2020-05-09 16:07:39 -06:00
certs
crypto	gcc-10: avoid shadowing standard library 'free()' in crypto	2020-05-09 15:58:04 -07:00
Documentation
drivers	Some GPIO fixes for the v5.7 kernel:	2020-05-12 10:39:34 -07:00
fs	Various gfs2 fixes	2020-05-12 10:32:32 -07:00
include	mm, memcg: fix inconsistent oom event behavior	2020-05-14 10:00:35 -07:00
init	Tracing fixes to previous fixes:	2020-05-12 11:06:26 -07:00
ipc
kernel	Tracing fixes to previous fixes:	2020-05-12 11:06:26 -07:00
lib
LICENSES
mm	block-5.7-2020-05-09	2020-05-10 11:16:07 -07:00
net	Fixes:	2020-05-11 12:04:52 -07:00
samples
scripts
security
sound
tools	Tracing fixes to previous fixes:	2020-05-12 11:06:26 -07:00
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS	Fixes for an endianness handling bug that prevented mounts on	2020-05-08 10:27:00 -07:00
Makefile	Linux 5.7-rc5	2020-05-10 15:16:58 -07:00
README

README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.