linux-kernel - Re: [RFC][PATCH 0/2] PF

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: <AANLkTimXpwFFOAk9ozZu=0srvL+cTEYkbD9qJjZudk5a@mail.gmail.com>
Date:	Mon, 20 Sep 2010 11:19:55 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
	Tejun Heo <tj@...nel.org>, Avi Kivity <avi@...hat.com>
Subject: Re: [RFC][PATCH 0/2] PF_flags cleaups

On Mon, Sep 20, 2010 at 11:03 AM, Peter Zijlstra <peterz@...radead.org> wrote:
>
> fs/proc/array.c:do_task_stat()

Ok, I doubt anybody cares. I think that thing is entirely historical,
and we probably should never have done it in the first place. I wonder
if we should just replace that field with a zero.

We've moved flag bits around in task->flags (and moved them to
thread->flags) before, so that /proc/<pid>/stat field has not been
stable historically either. I can't imagine what could break - it
would have broken many times before too.

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