Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753227AbcKHXvu (ORCPT ); Tue, 8 Nov 2016 18:51:50 -0500 Received: from resqmta-ch2-05v.sys.comcast.net ([69.252.207.37]:46576 "EHLO resqmta-ch2-05v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751594AbcKHXvt (ORCPT ); Tue, 8 Nov 2016 18:51:49 -0500 Date: Tue, 8 Nov 2016 17:51:46 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Andrew Morton cc: Thomas Garnier , Pekka Enberg , David Rientjes , Joonsoo Kim , Linux-MM , LKML , Greg Thelen , Vladimir Davydov , Michal Hocko Subject: Re: [PATCH v3 1/2] memcg: Prevent memcg caches to be both OFF_SLAB & OBJFREELIST_SLAB In-Reply-To: <20161107144931.edcf151a04f1af6d230b8a8a@linux-foundation.org> Message-ID: References: <1478553075-120242-1-git-send-email-thgarnie@google.com> <20161107141919.fe50cef419918c7a4660f3c2@linux-foundation.org> <20161107144931.edcf151a04f1af6d230b8a8a@linux-foundation.org> Content-Type: text/plain; charset=US-ASCII X-CMAE-Envelope: MS4wfOf9QU/3XTel5FsaXBCIz3Cv+LCeYPZDhBCJn8/IH5RtOi/kgUQOpxGOup3jqwKlt8RygX8Y7AhpMBXgIYjdDorByRbf96D62Z5P5GFNs/UNjolQavGD FIZzxpegQ7zCqWh6+zwF5K9uHnLJ+PY80jPwqoW2siH17nX7Y/Ig7SCdq+YSq5TYtNviGIZmt/8Teg0sScrkeC4ILOuSOk18Cg6inWhZHZJGvN0w4GeSvOND oCmLDdfyaFWXAackWjE8vgl7vIpv7bmReOUrWEKDmeJqbM6BXg+qzzSp2HdPGBC3HPTyTzYhLDWdK6e/FpCEGi1NXibTP7BfzSssBcQjl97m17l5HLoiRnUm YI6suXUGGvGYrib22JMjgtwJbRlUXTNd+LQHDtkpDseZkRk8oWAB2IBow4oWthMlB5ZYNrDLxs+6xAt5FHwK7MjwrtiyucouAgjZh50+3gwbktJHP9M= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 515 Lines: 14 On Mon, 7 Nov 2016, Andrew Morton wrote: > > I will add more details and send another round. > > Please simply send the additional changelog text in this thread - > processing an entire v4 patch just for a changelog fiddle is rather > heavyweight. I think this patch is good for future cleanup. We have had a case here where an internal flag was passed to kmem_cache_create that caused issues later. This should not happen. We need to guard against this in the future. Acked-by: Christoph Lameter