linux-kernel - Re: [PATCH v2] mm/memory-hotplug: Add sysfs hot-remove trigger

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

Message-ID: <20190226151856.GE10588@dhcp22.suse.cz>
Date:   Tue, 26 Feb 2019 16:18:56 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Robin Murphy <robin.murphy@....com>
Cc:     David Hildenbrand <david@...hat.com>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
        rafael@...nel.org, akpm@...ux-foundation.org, osalvador@...e.de
Subject: Re: [PATCH v2] mm/memory-hotplug: Add sysfs hot-remove trigger

On Tue 26-02-19 15:12:40, Robin Murphy wrote:
[...]
> The back of my mind is still ticking over trying to think up a really nice
> design for a self-contained debugfs or module-parameter interface completely
> independent of ARCH_MEMORY_PROBE - I'll probably keep using this hack
> locally to finish off the arm64 hot-remove stuff, but once that's done (or
> if inspiration strikes in the meantime) then I'll try to come back with a
> prototype of the developer interface that I'd find most useful.

Would it make more sense to add a module to the testing machinery?

-- 
Michal Hocko
SUSE Labs