linux-kernel - Re: [PATCH] ipc: always handle a new value of auto

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]

Message-ID: <53EC8369.8030406@colorfullife.com>
Date:	Thu, 14 Aug 2014 11:37:45 +0200
From:	Manfred Spraul <manfred@...orfullife.com>
To:	Andrey Vagin <avagin@...nvz.org>, linux-kernel@...r.kernel.org
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Mathias Krause <minipli@...glemail.com>,
	Joe Perches <joe@...ches.com>,
	Davidlohr Bueso <davidlohr@...com>
Subject: Re: [PATCH] ipc: always handle a new value of auto_msgmni

Hi Andrey,

On 08/13/2014 03:21 PM, Andrey Vagin wrote:
> proc_dointvec_minmax() returns zero, if a new value has been set.
> So we don't need to check all charectes have been handled.
What do you use auto_msgmni for?

I would propose to remove the whole logic - just always allow 32000 
message queues.

--
     Manfred
--
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/