Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753961AbaDRQdi (ORCPT ); Fri, 18 Apr 2014 12:33:38 -0400 Received: from g4t3426.houston.hp.com ([15.201.208.54]:31060 "EHLO g4t3426.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751139AbaDRQde (ORCPT ); Fri, 18 Apr 2014 12:33:34 -0400 Message-ID: <1397838812.19331.3.camel@buesod1.americas.hpqcorp.net> Subject: Re: [PATCH v3] ipc,shm: disable shmmax and shmall by default From: Davidlohr Bueso To: Manfred Spraul Cc: Andrew Morton , Michael Kerrisk , KOSAKI Motohiro , Kamezawa Hiroyuki , Greg Thelen , aswin@hp.com, LKML , "linux-mm@kvack.org" , linux-api@vger.kernel.org Date: Fri, 18 Apr 2014 09:33:32 -0700 In-Reply-To: <5350EFAA.2030607@colorfullife.com> References: <1397784345.2556.26.camel@buesod1.americas.hpqcorp.net> <5350EFAA.2030607@colorfullife.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 (3.6.4-3.fc18) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2014-04-18 at 11:26 +0200, Manfred Spraul wrote: > Hi Davidlohr, > > On 04/18/2014 03:25 AM, Davidlohr Bueso wrote: > > So a value of 0 bytes or pages, for shmmax and shmall, respectively, > > implies unlimited memory, as opposed to disabling sysv shared memory. > That might be a second risk: > Right now, a sysadmin can prevent sysv memory allocations with > > # sysctl kernel.shmall=0 Yeah, I had pointed this out previously, and it is addressed in the changelog. shmall = 0 directly contradicts size < shmmin = 1, so I don't know who's wrong there... -- 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/