Activity log for bug #260138

Date Who What changed Old value New value Message
2008-08-21 17:00:38 Kees Cook bug added bug
2008-08-21 17:03:39 Kees Cook bug assigned to x11proto-core (Ubuntu)
2008-08-21 17:07:31 Kees Cook bug assigned to xorg-server
2008-08-21 17:08:12 Kees Cook bug added attachment '200_raise_maxclients.patch' (x11proto-core patch for fdset)
2008-08-21 17:08:55 Kees Cook bug added attachment '200_raise_maxclients.patch' (xorg-server patch for maxclients)
2008-08-21 17:17:10 Bug Watch Updater xorg-server: status Unknown Confirmed
2008-08-21 18:33:17 Timo Aaltonen xorg-server: status New Confirmed
2008-08-21 18:33:17 Timo Aaltonen xorg-server: importance Undecided Wishlist
2008-08-21 18:33:17 Timo Aaltonen xorg-server: statusexplanation asked upstream about it. The patches are indeed in RHEL4, so they should be tested by now. They don't seem to qualify as-is to upstream though: 20:52 < ajax> you trade more clients for fewer resources per client 21:05 < ajax> the XID space is carved up weird 21:06 < ajax> (when i say "resources" i mean "protocol objects with an XID") 21:06 < ajax> top three bits are reserved (f*** you lisp), next eight bits are client id, the rest are for the client to allocate however it likes. 21:08 < ajax> so, with 256 clients, each of them can create up to 2 ^ (32 - 8 - 3) ~= 2 million resources 21:08 < ajax> 512 clients, one million resources each. etc. 21:09 < ajax> XIDs are allocated client-side to avoid round-tripping to the server on every resource creation, but that means you have to be able to allocate unique ids within each client. so you have to have some partition... 21:10 < ajax> i suppose the right way to fix this is to do a field survey of how many resources a typical "small" app and a typical "big" app use. 21:13 < ajax> on my machine, metacity is far and away the one with the most resources, and it's still down around the 2000 mark 21:13 < ajax> you do still want a fairly sizable allocation per client since XID reuse is pretty fast and furious, and requires a round trip through xc-misc 21:14 < ajax> and, you can't know that you're talking to an xlib that's new enough to know about the newer version of xc-misc 21:18 < ajax> this _might_ be a case where you could do protocol 11.1 meaningfully 21:18 < ajax> which would let the server assign huge ranges to 11.0 clients and tiny ones to 11.0 clients 21:18 < ajax> uh, tiny ones to 11.1 clients so, we can fix this in our packages, but it would not be the final solution.
2008-08-21 18:33:32 Timo Aaltonen x11proto-core: status New Confirmed
2008-08-21 18:33:32 Timo Aaltonen x11proto-core: importance Undecided Wishlist
2008-08-21 18:33:32 Timo Aaltonen x11proto-core: statusexplanation
2008-09-10 00:05:32 Bryce Harrington xorg-server: status Confirmed Triaged
2008-09-10 00:05:32 Bryce Harrington xorg-server: statusexplanation asked upstream about it. The patches are indeed in RHEL4, so they should be tested by now. They don't seem to qualify as-is to upstream though: 20:52 < ajax> you trade more clients for fewer resources per client 21:05 < ajax> the XID space is carved up weird 21:06 < ajax> (when i say "resources" i mean "protocol objects with an XID") 21:06 < ajax> top three bits are reserved (f*** you lisp), next eight bits are client id, the rest are for the client to allocate however it likes. 21:08 < ajax> so, with 256 clients, each of them can create up to 2 ^ (32 - 8 - 3) ~= 2 million resources 21:08 < ajax> 512 clients, one million resources each. etc. 21:09 < ajax> XIDs are allocated client-side to avoid round-tripping to the server on every resource creation, but that means you have to be able to allocate unique ids within each client. so you have to have some partition... 21:10 < ajax> i suppose the right way to fix this is to do a field survey of how many resources a typical "small" app and a typical "big" app use. 21:13 < ajax> on my machine, metacity is far and away the one with the most resources, and it's still down around the 2000 mark 21:13 < ajax> you do still want a fairly sizable allocation per client since XID reuse is pretty fast and furious, and requires a round trip through xc-misc 21:14 < ajax> and, you can't know that you're talking to an xlib that's new enough to know about the newer version of xc-misc 21:18 < ajax> this _might_ be a case where you could do protocol 11.1 meaningfully 21:18 < ajax> which would let the server assign huge ranges to 11.0 clients and tiny ones to 11.0 clients 21:18 < ajax> uh, tiny ones to 11.1 clients so, we can fix this in our packages, but it would not be the final solution.
2008-09-10 00:06:12 Bryce Harrington x11proto-core: status Confirmed Triaged
2008-11-21 18:35:25 Kees Cook x11proto-core: milestone jaunty-alpha-4
2009-01-12 21:34:26 Bryce Harrington xorg-server: status Triaged In Progress
2009-01-12 21:34:26 Bryce Harrington xorg-server: statusexplanation Plan is to tackle this post-alpha3, as it will require changing x11proto-core first so will be safest to do post-release.
2009-01-27 07:16:13 Bryce Harrington xorg-server: assignee bryceharrington
2009-01-27 07:16:13 Bryce Harrington xorg-server: statusexplanation Plan is to tackle this post-alpha3, as it will require changing x11proto-core first so will be safest to do post-release.
2009-02-05 04:40:41 Bryce Harrington bug added attachment 'xorg-server_1.5.99.902-0ubuntu2.debdiff' (xorg-server_1.5.99.902-0ubuntu2.debdiff)
2009-02-05 04:59:19 Bryce Harrington bug added attachment 'x11proto-core_7.0.14-1ubuntu1.debdiff' (x11proto-core_7.0.14-1ubuntu1.debdiff)
2009-02-05 05:44:34 Bryce Harrington bug added attachment 'x11proto-core_7.0.14-1ubuntu1.debdiff' (x11proto-core_7.0.14-1ubuntu1.debdiff)
2009-02-05 08:10:53 Bryce Harrington xorg-server: status In Progress Fix Committed
2009-02-05 08:10:53 Bryce Harrington xorg-server: statusexplanation Patch committed to git; will be uploaded after freeze is lifted.
2009-02-05 08:12:24 Bryce Harrington x11proto-core: status Triaged In Progress
2009-02-05 08:12:24 Bryce Harrington x11proto-core: statusexplanation Patch for x11proto-core is ready to go once archive unfrozen.
2009-02-06 09:00:41 Launchpad Janitor xorg-server: status Fix Committed Fix Released
2009-02-09 21:59:57 Bryce Harrington xorg-server: status Fix Released Triaged
2009-02-09 21:59:57 Bryce Harrington xorg-server: statusexplanation Patch committed to git; will be uploaded after freeze is lifted. Reverted patch, since it breaks -nvidia. Sorry, it seems to do this properly requires a rev of the X11 protocol, which is a much bigger endeavor than can be done in Ubuntu. Upstream seems open to doing this though, but as this is a wishlist item, I would prefer you would please work with upstream (ajax) directly on this.
2009-02-09 22:00:28 Bryce Harrington x11proto-core: status In Progress Triaged
2009-02-09 22:00:28 Bryce Harrington x11proto-core: statusexplanation Patch for x11proto-core is ready to go once archive unfrozen.
2009-02-09 22:00:56 Bryce Harrington title Xorg needs client limit raised (needs x11 protocol update) Xorg needs client limit raised
2009-02-09 22:01:12 Bryce Harrington xorg-server: assignee bryceharrington
2009-02-09 22:01:12 Bryce Harrington xorg-server: statusexplanation Reverted patch, since it breaks -nvidia. Sorry, it seems to do this properly requires a rev of the X11 protocol, which is a much bigger endeavor than can be done in Ubuntu. Upstream seems open to doing this though, but as this is a wishlist item, I would prefer you would please work with upstream (ajax) directly on this.
2010-02-22 22:34:53 Launchpad Janitor branch linked lp:ubuntu/xorg-server
2010-09-11 13:02:03 Bug Watch Updater xorg-server: importance Unknown Medium
2011-01-24 13:39:47 Bug Watch Updater xorg-server: importance Medium Unknown
2011-03-21 14:13:34 Bug Watch Updater xorg-server: importance Unknown Medium
2011-03-23 01:52:03 Hew removed subscriber Hew McLachlan
2011-05-11 14:52:25 Timo Aaltonen x11proto-core (Ubuntu): status Triaged Won't Fix
2011-05-11 14:52:25 Timo Aaltonen x11proto-core (Ubuntu): milestone jaunty-alpha-4
2011-05-11 14:52:34 Timo Aaltonen xorg-server (Ubuntu): status Triaged Won't Fix