[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1438958196-23036-1-git-send-email-daniel@zonque.org>
Date: Fri, 7 Aug 2015 16:36:32 +0200
From: Daniel Mack <daniel@...que.org>
To: gregkh@...uxfoundation.org
Cc: dh.herrmann@...il.com, tixxdz@...ndz.org, teg@...m.no,
linux-kernel@...r.kernel.org, Daniel Mack <daniel@...que.org>
Subject: [PATCH 0/4] kdbus: name registry cleanup patches
Hi Greg,
Here are some patches for kdbus-next David and I prepared:
* The first one cleans up the name registry code and brings the name
queuing logic in sync with what the DBus spec requires. We were off
in some small details concerning flags updates of already queued
names.
* The second one adds two more return flags in the name queuing logic,
so userspace has better ways of knowing what effect a name acquisition
call had.
* Number three is a small cleanup that makes sure we never return
negative return codes from ioctls if we modified any internal state.
This is a rule all other command dispatchers follow as well.
* The last one adds more selftests for the name registry, covering the
newly added flags.
None of these patches is critical, and everything has been running well
on our machines for a while.
Thanks,
Daniel
Daniel Mack (1):
kdbus: selftests: add more name registry tests
David Herrmann (3):
kdbus: restructure name-registry to follow dbus-spec
kdbus: inform caller about exact updates on NAME_ACQUIRE
kdbus: never return <0 from ioctls if we changed state
include/uapi/linux/kdbus.h | 4 +
ipc/kdbus/connection.c | 53 +-
ipc/kdbus/connection.h | 9 +-
ipc/kdbus/metadata.c | 21 +-
ipc/kdbus/names.c | 762 ++++++++++++++++-------------
ipc/kdbus/names.h | 55 ++-
tools/testing/selftests/kdbus/kdbus-test.c | 6 +
tools/testing/selftests/kdbus/kdbus-test.h | 1 +
tools/testing/selftests/kdbus/test-chat.c | 6 +-
tools/testing/selftests/kdbus/test-names.c | 140 ++++--
10 files changed, 633 insertions(+), 424 deletions(-)
--
2.4.3
--
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