linux-kernel - Re: [RFC][PATCH 0/2] New API to change the IDs of an existing IPC

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] [day] [month] [year] [list]

Date:	Mon, 01 Oct 2007 09:19:18 +0200
From:	Pierre Peiffer <pierre.peiffer@...l.net>
To:	Michael Kerrisk <mtk.linux.lists@...il.com>
Cc:	linux-kernel@...r.kernel.org, containers@...ts.osdl.org,
	mtk-manpages@....net
Subject: Re: [RFC][PATCH 0/2] New API to change the IDs of an existing IPC

Michael Kerrisk a écrit :
> Hi Pierre,
> 
>>         As I'm seeing some discussion/interest about IPC, I would like to propose
>>  these patches, which provide an easy way to change the ID of an exiting IPC.
>> This work is done around the checkpoint/restart of applications. In the case of
>> the IPCs, we need (among others) this functionality.
> 
> Can you give some more detailed explanation of why this
> functionaility is needed.  

Sure; in the case of the checkpoint/restart, when you restart an application, what you want is to recreate all system ressources with the same properties they had, when you have checkpointed it.
For IPCs, this means that you need to recreate all the IPCs with the same IDs (at least).
For now, this ID is computed by the system when an IPC is created and you can't specify or modify it.

These patches give you the possibility of changing this ID once the IPC is created.

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