linux-kernel - Re: [PATCH] sched: share task comm length value to userspace

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, 5 Sep 2011 12:47:26 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Vladimir Zapolskiy <vz@...ia.com>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] sched: share task comm length value to userspace

On Mon,  5 Sep 2011 21:38:01 +0300
Vladimir Zapolskiy <vz@...ia.com> wrote:

> This change allows to get a defined length of task comm in
> userspace. For a moment this value is implied at least in two cases:
> * max length of comm value got from /proc/$pid/stat
> * max string length argument of prctl(PR_[SG]ET_NAME, ...)
> 
> For these reasons it becomes desirable to impart task comm max length
> value to userspace.

I'm sorry but I don't like doing this.

The moment we do this, we never can increase it anymore since userspace
might be using it for its own uses and we'd break it if we changed
this value.

If we need to export this, we should export it in /proc or /sys
somewhere as a dynamic value.....



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/