linux-kernel - [PATCH 0/4 v2] show

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>] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 17 Jan 2017 10:15:39 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Johannes Weiner <hannes@...xchg.org>, Mel Gorman <mgorman@...e.de>,
        Vlastimil Babka <vbabka@...e.cz>,
        David Rientjes <rientjes@...gle.com>, <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Chris Metcalf <cmetcalf@...lanox.com>,
        "David S. Miller" <davem@...emloft.net>,
        Fenghua Yu <fenghua.yu@...el.com>,
        Guan Xuetao <gxt@...c.pku.edu.cn>,
        Helge Deller <deller@....de>,
        "James E.J. Bottomley" <jejb@...isc-linux.org>,
        Michal Hocko <mhocko@...e.com>, Tony Luck <tony.luck@...el.com>
Subject: [PATCH 0/4 v2] show_mem updates 

Hi,
the previous version has been posted [1] and there didn't seem to be
any opposition so I am reposting it for inclusion. There was only
one change and warn_alloc_show_mem does cpuset_print_current_mems_allowed
now. Besides that acks have been added.

This is a mixture of one bug fix (patch 1), an enhancement (patch 2)
and cleanups (the rest of the series). First two patches should be
really straightforward. Patch 3 removes some arch specific show_mem
implementations because I think they are quite outdated and do not
really serve any useful purpose anymore. I think we should really strive
to have a consistent show_mem output regardless of the architecture. If
some architecture is really special and wants to dump something
additional we should do that via an arch specific hook.

The last patch adds nodemask parameter so that we do not rely on
the hardcoded mems_allowed of the current task when doing the node
filtering.  I consider this more a cleanup than a fix because basically
all users use a nodemask which is a subset of mems_allowed. There is
only one call path in the memory hotplug which doesn't comply with this
but that is hardly something to worry about.

[1] http://lkml.kernel.org/r/20170112131659.23058-1-mhocko@kernel.org

This is on top of the current mmotm (mmotm-2016-12-19-16-31) tree .
Michal Hocko (4):
      mm, page_alloc: do not report all nodes in show_mem
      mm, page_alloc: warn_alloc print nodemask
      arch, mm: remove arch specific show_mem
      lib/show_mem.c: teach show_mem to work with the given nodemask

 arch/ia64/mm/init.c                 | 48 ------------------------------------
 arch/parisc/mm/init.c               | 49 -------------------------------------
 arch/powerpc/xmon/xmon.c            |  2 +-
 arch/sparc/kernel/setup_32.c        |  2 +-
 arch/sparc/mm/init_32.c             | 11 ---------
 arch/tile/mm/pgtable.c              | 45 ----------------------------------
 arch/unicore32/mm/init.c            | 44 ---------------------------------
 drivers/net/ethernet/sgi/ioc3-eth.c |  2 +-
 drivers/tty/sysrq.c                 |  2 +-
 drivers/tty/vt/keyboard.c           |  2 +-
 include/linux/mm.h                  |  9 +++----
 lib/show_mem.c                      |  4 +--
 mm/nommu.c                          |  6 ++---
 mm/oom_kill.c                       |  2 +-
 mm/page_alloc.c                     | 49 ++++++++++++++++++++-----------------
 mm/vmalloc.c                        |  4 +--
 16 files changed, 44 insertions(+), 237 deletions(-)