linux-kernel - Re: [RFC: 2.6 patch] let GROUP

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:	Tue, 27 May 2008 13:47:29 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Mike Galbraith <efault@....de>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	vatsa <vatsa@...ibm.com>
Subject: Re: [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN

On Tue, 2008-05-27 at 11:58 +0300, Adrian Bunk wrote: 

> I therefore suggest this patch to let GROUP_SCHED depend on BROKEN.

NAK - Most if not all issues have fixes or specific reverts already.

Your suggestion is really quite ridiculous and offensive to me. BROKEN
is for stuff that crashes kernels or corrupts user data. Group
scheduling does neither.

As I've said - and which you so 'tactfully' quoted - group scheduling is
a mathmatically complex topic that we are improving actively. The
feature is not enabled by default and it depends on EXPERIMENTAL.

Adrian - if you care about the subject so much - dive into the code and
help us, instead of becoming an obstacle. These past years you've shown
you're capable of understanding trivial C snippets, here is an
opportunity to show you can do real stuff too.

FYI your attitude in the past few weeks is getting on my nerves - you
act all self important but have not made a single contribution to the
kernel above the level of a janitor-newbie.

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