Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754450Ab3EaJ1O (ORCPT ); Fri, 31 May 2013 05:27:14 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:59283 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753082Ab3EaJ1K (ORCPT ); Fri, 31 May 2013 05:27:10 -0400 Date: Fri, 31 May 2013 11:27:04 +0200 From: Ingo Molnar To: KOSAKI Motohiro Cc: Christoph Lameter , Peter Zijlstra , Al Viro , Vince Weaver , LKML , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , trinity@vger.kernel.org, Andrew Morton , Linus Torvalds , Roland Dreier , infinipath@qlogic.com, "linux-mm@kvack.org" , linux-rdma@vger.kernel.org, Or Gerlitz , Hugh Dickins Subject: Re: [RFC][PATCH] mm: Fix RLIMIT_MEMLOCK Message-ID: <20130531092704.GA30394@gmail.com> References: <20130523163901.GG23650@twins.programming.kicks-ass.net> <0000013ed28b638a-066d7dc7-b590-49f8-9423-badb9537b8b6-000000@email.amazonses.com> <20130524140114.GK23650@twins.programming.kicks-ass.net> <0000013ed732b615-748f574f-ccb8-4de7-bbe4-d85d1cbf0c9d-000000@email.amazonses.com> <20130527064834.GA2781@laptop> <0000013eec0006ee-0f8caf7b-cc94-4f54-ae38-0ca6623b7841-000000@email.amazonses.com> <20130529075845.GA24506@gmail.com> <51A65CC0.3050800@gmail.com> <20130530063205.GA5310@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1174 Lines: 34 * KOSAKI Motohiro wrote: > >> I'm unhappy you guys uses offensive word so much. Please cool down all > >> you guys. :-/ In fact, _BOTH_ the behavior before and after Cristoph's > >> patch doesn't have cleaner semantics. > > > > Erm, this feature _regressed_ after the patch. All other concerns are > > secondary. What's so difficult to understand about that? > > Because it is not new commit at all. Christoph's patch was introduced > 10 releases before. That's indeed sad - resource limits are not typically tested by apps. The lack of Cc:s to people affected also helped hide the effects of the change. > $ git describe bc3e53f682 > v3.1-7235-gbc3e53f > > If we just revert it, we may get another and opposite regression report. > I'm worried about it. Moreover, I don't think discussion better fix is > too difficult for us. Sure, I agree that a fix is generally better. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/