[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121218123601.113a29c0.akpm@linux-foundation.org>
Date: Tue, 18 Dec 2012 12:36:01 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stanislav Kinsbursky <skinsbursky@...allels.com>
Cc: serge.hallyn@...onical.com, ebiederm@...ssion.com,
linux-kernel@...r.kernel.org, xemul@...allels.com,
catalin.marinas@....com, will.deacon@....com, jmorris@...ei.org,
cmetcalf@...era.com, joe.korty@...r.com, dhowells@...hat.com,
dledford@...hat.com, viro@...iv.linux.org.uk,
kosaki.motohiro@...fujitsu.com, linux-api@...r.kernel.org,
serue@...ibm.com, tglx@...utronix.de, paulmck@...ux.vnet.ibm.com,
devel@...nvz.org, mtk.manpages@...il.com,
Sasha Levin <sasha.levin@...cle.com>,
Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: [RFC PATCH v8 0/5] IPC: checkpoint/restore in userspace
enhancements
On Wed, 24 Oct 2012 19:34:51 +0400
Stanislav Kinsbursky <skinsbursky@...allels.com> wrote:
> This respin of the patch set was significantly reworked. Most part of new API
> was replaced by sysctls (by one per messages, semaphores and shared memory),
> allowing to preset desired id for next new IPC object.
>
> This patch set is aimed to provide additional functionality for all IPC
> objects, which is required for migration of these objects by user-space
> checkpoint/restore utils (CRIU).
>
> The main problem here was impossibility to set up object id. This patch set
> solves the problem by adding new sysctls for preset of desired id for new IPC
> object.
>
> Another problem was to peek messages from queues without deleting them.
> This was achived by introducing of new MSG_COPY flag for sys_msgrcv(). If
> MSG_COPY flag is set, then msgtyp is interpreted as message number.
According to my extensive records, Sasha hit a bug in
ipc-message-queue-copy-feature-introduced.patch and Fengguang found a
bug in
ipc-message-queue-copy-feature-introduced-cleanup-do_msgrcv-aroung-msg_copy-feature.patch
It's not obvious (to me) that these things have been identified and
fixed. What's the status, please?
--
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/
Powered by blists - more mailing lists