linux-kernel - whatever happened to making setpriority POSIX-compliant?

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

Message-ID: <4EE11903.7060809@genband.com>
Date:	Thu, 08 Dec 2011 14:07:31 -0600
From:	Chris Friesen <chris.friesen@...band.com>
To:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: whatever happened to making setpriority POSIX-compliant?

Back in 2008 there was a patch proposed to make setpriority() apply to 
processes as a whole:

[PATCH] make setpriority POSIX compliant; introduce PRIO_THREAD extension.

Ulrich agreed to it in theory, Christoph Hellwig proposed a way to make 
it backwards-compatible, and then nothing happened.

Is this something that we'd ever want to fix up, or is the current 
behaviour good enough?

Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@...band.com
www.genband.com
--
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/