CRIU can dump queued data for unix and tcp sockets,
now it's time for netlink sockets.

Here are there questions.
* How to dump data from a receive queue
  We can set peeking offset like we do for unix sockets.

* How to restore data back to a receive queue
  I suggest to add a repair mode like we do for tcp sockets.

* When we can dump data from a receive queue.
  I think we can do this only if a socket doesn't have a running callback.

Cc: Pavel Emelyanov <xe...@virtuozzo.com>
Cc: "David S. Miller" <da...@davemloft.net>
Cc: Ken-ichirou MATSUZAWA <chama...@gmail.com>
Cc: Daniel Borkmann <dan...@iogearbox.net>
Cc: Florian Westphal <f...@strlen.de>
Cc: Herbert Xu <herb...@gondor.apana.org.au>
Cc: David Herrmann <dh.herrm...@gmail.com>
Cc: Christophe Ricard <christophe.ric...@gmail.com>

Andrey Vagin (3):
  netlink: allow to set peeking offset for sockets
  netlink: add an ability to restore messages in a receive queue
  netlink/diag: report flags for netlink sockets

 include/uapi/linux/netlink.h      |  1 +
 include/uapi/linux/netlink_diag.h | 10 +++++
 net/netlink/af_netlink.c          | 82 ++++++++++++++++++++++++++-------------
 net/netlink/af_netlink.h          |  9 +++++
 net/netlink/diag.c                | 25 ++++++++++++
 5 files changed, 99 insertions(+), 28 deletions(-)

-- 
2.5.5

Reply via email to