linux-kernel - [PATCH] kdbus: raise hard-coded limit of matches

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

Message-Id: <1441357355-17619-1-git-send-email-dh.herrmann@gmail.com>
Date:	Fri,  4 Sep 2015 11:02:35 +0200
From:	David Herrmann <dh.herrmann@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Daniel Mack <daniel@...que.org>, tixxdz@...ndz.org,
	David Herrmann <dh.herrmann@...il.com>
Subject: [PATCH] kdbus: raise hard-coded limit of matches

The current MATCH limit is far too low. We allow more bus-connections per
user than peers to install matches. Raise the limit to a reasonable
default of 4096. The current limit is exactly enough to run Gnome, but
can be easily exceeded by starting some additional service providers.
With the raised limit, we should be fine for the near future.

Some day, we might decide to make those limits dynamically configurable.
However, that needs some more benchmarking, until we can figure out
perfect defaults.

Signed-off-by: David Herrmann <dh.herrmann@...il.com>
---
 ipc/kdbus/limits.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ipc/kdbus/limits.h b/ipc/kdbus/limits.h
index c54925a..bd47119 100644
--- a/ipc/kdbus/limits.h
+++ b/ipc/kdbus/limits.h
@@ -41,7 +41,7 @@
 #define KDBUS_SYSNAME_MAX_LEN			63
 
 /* maximum number of matches per connection */
-#define KDBUS_MATCH_MAX				256
+#define KDBUS_MATCH_MAX				4096
 
 /* maximum number of queued messages from the same individual user */
 #define KDBUS_CONN_MAX_MSGS			256
-- 
2.5.1

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