linux-kernel - Re: [PATCH] sched: remove noop in pre_schedule

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

Date:	Mon, 06 Jun 2011 09:25:34 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Hillf Danton <dhillf@...il.com>
Cc:	Yong Zhang <yong.zhang0@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Mike Galbraith <efault@....de>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] sched: remove noop in pre_schedule_rt()

On Mon, 2011-06-06 at 21:14 +0800, Hillf Danton wrote:

> The work was repeated not only by Yong, you see, almost
> impossible, which shows RT scheduling was and is
> attracting minds, and will be as well, right?

It was an obvious fix, hardly impossible for it to be done twice. This
happens all the time in the kernel. Especially if for some reason a fix
doesn't make it in. This fix didn't make it in simply because it wasn't
one of my normal branches I push to Ingo, and it was at a time that we
all were quite busy and it was simply overlooked.

But yes, the RT scheduler (and the scheduler itself) always attracts
newcomers, and we welcome them. Nothing curious or unusually about it.

-- Steve

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