linux-kernel - Re: per-thread rusage

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

Date:	Mon, 9 Apr 2007 17:42:01 -0700
From:	William Lee Irwin III <wli@...omorphy.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Eric Dumazet <dada1@...mosbay.com>, linux-kernel@...r.kernel.org
Subject: Re: per-thread rusage

On Wed, 4 Apr 2007 11:10:50 -0700 William Lee Irwin III <wli@...omorphy.com> wrote:
>> Respun vs. 2.6.21-rc5-mm4, still untested. Also...
>> Signed-off-by: William Irwin <bill.irwin@...cle.com>
[...]

On Mon, Apr 09, 2007 at 04:53:15PM -0700, Andrew Morton wrote:
> Seems sane.  Could we please get it tested and get a full description in
> place?  Something which provides enough detail for the manpage maintainers.
> Also, a quick comparison between Linux's RUSAGE_THREAD and $other-os's
> implementations would reduce the possibility of silly, cast-in-stone
> incompatabilities.

The latter is the more serious of the two. I'll go about investigating
that as the primary task here. Testing and a more verbose patch
description are clearly very little work.

General maintenance-relevant commentary: This patch arose from an
observation of a lacuna in the API. There are no bugs or apps broken
awaiting this as a fix, so it's not needed by 2.6.22 or otherwise
urgently. My use for it is report generation in VM (and possibly other)
testcases. The ack-in-concept is good enough for me to go about
sweeping up the OS/standards compatibility, testing, and documentation
issues in the near future prior to resubmission.

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