linux-kernel - Re: [PATCH] task_struct: remove writeonly counters

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]

Message-Id: <20060731210107.89cab506.akpm@osdl.org>
Date:	Mon, 31 Jul 2006 21:01:07 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Alexey Dobriyan <adobriyan@...il.com>
Cc:	linux-kernel@...r.kernel.org, Jay Lan <jlan@...r.sgi.com>
Subject: Re: [PATCH] task_struct: remove writeonly counters

On Tue, 1 Aug 2006 06:29:51 +0400
Alexey Dobriyan <adobriyan@...il.com> wrote:

> ...
>
> +++ b/include/linux/sched.h
> @@ -962,8 +962,6 @@ #endif
>   * to a stack based synchronous wait) if its doing sync IO.
>   */
>  	wait_queue_t *io_wait;
> -/* i/o counters(bytes read/written, #syscalls */
> -	u64 rchar, wchar, syscr, syscw;

This is kinda funny.  These fields were added a year and a half ago, with
the intention that the info be made available to userspace.  But then
things got horridly stuck.  It's only in the past couple of weeks that we've
gained appropriate reporting-to-userspace infrastructure to be able to use
these fields.

And lo, on the very day when you propose removing these fields, Jay posts a
new patchset ("add CSA accounting to taskstats") which finally gets around to
using them.

So..  we should keep these fields for now - we can perhaps remove them (in
less than 1.5 years) if for some reason the CSA patches crash and burn (I
don't think they will).

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