From owner-p4-projects@FreeBSD.ORG Sun Jan 16 14:51:41 2011 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 3A4E31065672; Sun, 16 Jan 2011 14:51:41 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1266106566B for ; Sun, 16 Jan 2011 14:51:40 +0000 (UTC) (envelope-from trasz@freebsd.org) Received: from skunkworks.freebsd.org (skunkworks.freebsd.org [IPv6:2001:4f8:fff6::2d]) by mx1.freebsd.org (Postfix) with ESMTP id DEA138FC0C for ; Sun, 16 Jan 2011 14:51:40 +0000 (UTC) Received: from skunkworks.freebsd.org (localhost [127.0.0.1]) by skunkworks.freebsd.org (8.14.4/8.14.4) with ESMTP id p0GEpeB6050620 for ; Sun, 16 Jan 2011 14:51:40 GMT (envelope-from trasz@freebsd.org) Received: (from perforce@localhost) by skunkworks.freebsd.org (8.14.4/8.14.4/Submit) id p0GEpejR050617 for perforce@freebsd.org; Sun, 16 Jan 2011 14:51:40 GMT (envelope-from trasz@freebsd.org) Date: Sun, 16 Jan 2011 14:51:40 GMT Message-Id: <201101161451.p0GEpejR050617@skunkworks.freebsd.org> X-Authentication-Warning: skunkworks.freebsd.org: perforce set sender to trasz@freebsd.org using -f From: Edward Tomasz Napierala To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 187861 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2011 14:51:41 -0000 http://p4web.freebsd.org/@@187861?ac=10 Change 187861 by trasz@trasz_victim on 2011/01/16 14:50:56 Update TODO. Affected files ... .. //depot/projects/soc2009/trasz_limits/TODO#39 edit Differences ... ==== //depot/projects/soc2009/trasz_limits/TODO#39 (text+ko) ==== @@ -32,8 +32,6 @@ level containers could overflow), and atomic(9) doesn't support 64 bit values on 32 bit platforms. - - Rethink HRL locking. - - Consider replacing proc pointer with thread pointer in rusage_add(9) et al. In most cases caller uses 'td->td_proc' anyway, and passing thread would allow the HRL code to send a signal to the offending thread instead of the @@ -102,7 +100,7 @@ HRL-specific issues: - - Reconsider setrlimit(2) handling. + - Reconsider bringing back setrlimit(2) handling. - Reconsider bringing back per-group limits. @@ -112,7 +110,3 @@ if one adds rule with 'sig*' action, the signal will be sent to the parent instead of the child. - - Add sorting to hrl(8). - - - Should priv(9) checking be done by HRL, or by the callers? -