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: <53EFBF1C.5060407@colorfullife.com>
Date:	Sat, 16 Aug 2014 22:29:16 +0200
From:	Manfred Spraul <manfred@...orfullife.com>
To:	Andrew Vagin <avagin@...allels.com>
CC:	Andrey Vagin <avagin@...nvz.org>, linux-kernel@...r.kernel.org,
	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 Andrew,

On 08/14/2014 03:34 PM, Andrew Vagin wrote:
> On Thu, Aug 14, 2014 at 11:37:45AM +0200, Manfred Spraul wrote:
>> Hi Andrey,
>>
>> [...]
>> What do you use auto_msgmni for? 
> We disable it to check that criu restores a value of the msgmni sysctl correctly.
>
> https://github.com/xemul/criu/blob/master/test/zdtm/live/static/ipc_namespace.c
Thanks for the link, if I see it right, my patch would break your code:

http://marc.info/?l=linux-kernel&m=140782863804950

It removes auto_msgmni - and
What do you think, should I leave auto_msgmni as a stale variable, 
perhaps with a pr_info() that it doesn't have any effect?


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