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  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]
Date:   Fri, 10 Aug 2018 15:00:52 +0200
From:   Michal Hocko <>
To:     Rashmica Gupta <>
Cc:     Andrew Morton <>,,,,,,,,,,,
        Vlastimil Babka <>,,
        Bjorn Helgaas <>,,,,,
        Mike Rapoport <>
Subject: Re: [PATCH v3] resource: Merge resources on a node when hot-adding

On Fri 10-08-18 16:55:40, Rashmica Gupta wrote:
> Most memory hotplug/hotremove seems to be block or section based, and
> always adds and removes memory at the same place.

Yes and that is hard wired to the memory hotplug code. It is not easy to
make it work outside of section units restriction. So whatever your
memtrace is doing and if it relies on subsection hotplug it cannot
possibly work with the current code.

I didn't get to review your patch but if it is only needed for an
unmerged code I would rather incline to not merge it unless it is a
clear win to the resource subsystem. A report from Oscar shows that this
is not the case though.

Michal Hocko

Powered by blists - more mailing lists