linux-kernel - Re: [PATCH] cpusets: Allocate heap only when required

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]

Date:	Fri, 24 Jan 2014 05:59:52 -0500
From:	Tejun Heo <tj@...nel.org>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Li Zefan <lizefan@...wei.com>,
	Viresh Kumar <viresh.kumar@...aro.org>, mingo@...nel.org,
	peterz@...radead.org, linaro-kernel@...ts.linaro.org,
	patches@...aro.org, linux-kernel@...r.kernel.org,
	Cgroups <cgroups@...r.kernel.org>
Subject: Re: [PATCH] cpusets: Allocate heap only when required

Hey,

On Fri, Jan 24, 2014 at 02:51:12AM -0800, David Rientjes wrote:
> Nobody is depending on shit, the patch is removing a completely pointless 
> memory allocation in braindead cpuset code.  What you think is "harmful" 
> or "more harmful" is irrelevant, but nobody said anything about depending 
> on that behavior to do anything.

Weren't you talking something of that effect in memcg?  Or was it
Michal?  At any rate, I think you're missing the point why Li replied
that it's harmless.  He, I think, meant that it doesn't make any
semantical difference to userland, so your reply saying that it's not
harmless listing the failure mode under memory pressure seemed
misleading, so I thought clarification was necessary.  Probably my
(false?) memory of you talking about that contributed.  Anyways, we
agree.  Don't depend on it.

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/