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

Message-Id: <20070928165829.5da76796.Pierre.Peiffer@bull.net>
Date:	Fri, 28 Sep 2007 16:58:29 +0200
From:	Pierre Peiffer <Pierre.Peiffer@...l.net>
To:	linux-kernel@...r.kernel.org
Cc:	containers@...ts.osdl.org
Subject: [RFC][PATCH 0/2] New API to change the IDs of an existing IPC

Hi,

	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.

May be there is some other interest about this, so, the RFC concerns both the coding and the interest.

The first patch provide the functionality in kernel side, the second export it in user space. They apply on top of the latest -rc8 kernel. I can adapt them for the latest -mm.

Thanks,

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