Re: [CRIU] [PATCH 0/5] IPC: checkpoint/restore in userspace enhancements

[Kinsbursky Stanislav]

Hello, Andrew.
Are you going to take this patch set?


09.02.2012 22:01, Stanislav Kinsbursky ÐÐÑÐÑ:
> This patch set aimed to provide additional functionality for all IPC objects,
> which is required for migration these objects by user-space checkpoint/restore
> utils.
> The main problem here was impossibility to set up object id. This patch set
> solves the problem in two steps:
> 1) Makes it possible to create new object (shared memory, semaphores set or
> messages queue) with ID, equal to passed key.
> 2) Makes it possible to change existent object key.
>
> The following series consists of:
>
> ---
>
> Stanislav Kinsbursky (5):
>        ipc: "use key as id" functionality for resource get system call introduced
>        ipc: segment key change helper introduced
>        ipc: add new SHM_SET command for sys_shmctl() call
>        ipc: add new MSG_SET command for sys_msgctl() call
>        ipc: add new SEM_SET command for sys_semctl() call
>
>
>   include/linux/ipc.h        |    1 +
>   include/linux/msg.h        |    1 +
>   include/linux/sem.h        |    1 +
>   include/linux/shm.h        |    1 +
>   ipc/compat.c               |    9 +++++++
>   ipc/msg.c                  |   14 +++++++++-
>   ipc/sem.c                  |   11 +++++++-
>   ipc/shm.c                  |   14 +++++++++-
>   ipc/util.c                 |   59 +++++++++++++++++++++++++++++++++++++++++---
>   ipc/util.h                 |    3 ++
>   security/selinux/hooks.c   |    3 ++
>   security/smack/smack_lsm.c |    3 ++
>   12 files changed, 110 insertions(+), 10 deletions(-)
>
> _______________________________________________
> CRIU mailing list
> CRIU@xxxxxxxxxx
> https://openvz.org/mailman/listinfo/criu


--
Best regards,
Stanislav Kinsbursky

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/