linux-kernel - Re: [PATCH 0/7] shrinker debugging improvements

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

Message-ID: <ZWW6Efq6QAEQwsnl@tiehlicka>
Date:   Tue, 28 Nov 2023 10:59:45 +0100
From:   Michal Hocko <mhocko@...e.com>
To:     Kent Overstreet <kent.overstreet@...ux.dev>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] shrinker debugging improvements

On Wed 22-11-23 18:25:05, Kent Overstreet wrote:
> This patchset does a few things to aid in OOM debugging, in particular
> when shrinkers are involved:
> 
>  - improves the show_mem OOM report: it now reports on shrinkers, and
>    for both shrinkers and slab we only report the top 10 entries,
>    sorted, not the full list
> 
>  - add shrinker_to_text(), for the show_mem report and debugfs, and a
>    an optional shrinker.to_text() callback to report extra
>    driver-specific information
> 
>  - add extra counters for the shrinker_to_text() report
> 
>  - implement shrinker.to_text() for bcachefs, giving an example of how
>    to use the callbacks

Could you expand some more about all these? What is the additional
information you can get and how usable that is? Some examples would be
really useful in the cover letter to establish grounds for the
discussion.

/me is looking at patches to find out more.
-- 
Michal Hocko
SUSE Labs