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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20170828094316.GF17097@dhcp22.suse.cz>
Date:   Mon, 28 Aug 2017 11:43:16 +0200
From:   Michal Hocko <mhocko@...nel.org>
To:     KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:     linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>
Subject: timeout for memory offline

Hi Kamezawa,
I've been wondering why do we have a hardcoded 120s timeout for
offline_pages. This goes all the way down to when the offlining
has been implemented. I am asking because I have seen many cases
where memory offline fails just because of the timeout on a large
machines under heavy memory load during offline operation. So I
am really wondering whether we should make the timeout configurable or
just remove it altogether. I would be more inclined for the later
but there might have been an explicit reason for the timeout which is
not clear to me. Could you clarify?
-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ