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
| ||
|
Date: Fri, 27 Nov 2009 07:21:47 +0100 From: Ingo Molnar <mingo@...e.hu> To: Tejun Heo <tj@...nel.org> Cc: Peter Zijlstra <peterz@...radead.org>, Steven Rostedt <rostedt@...dmis.org>, Fr??d??ric Weisbecker <fweisbec@...il.com>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Mike Galbraith <efault@....de>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: [PATCH 1/4 tip/sched/core] sched: rename preempt_notifier to sched_notifier and always enable it * Tejun Heo <tj@...nel.org> wrote: > 11/27/2009 03:13 PM, Ingo Molnar wrote: > >>> My position on this is rather clear: i want no new callbacks and no > >>> changes to callbacks in the scheduler until this situation is cleaned > >>> up. Five callback sites are _way_ too much - so if you want to add > >>> callbacks or change them, please clean it up and improve it first. > >> > >> Even changes which cause no functional differences? [...] > > > > Such as enabling preempt notifiers unconditionally? That's a functional > > change - it turns a so-far optional callback into an essentially > > mandatory one. > > No, I'm not gonna do that. Just patches to reorganize code so that > unnecessary conflicts won't occur. There will be NO functional > changes. Not without the other changes - which you want to do too, right? Please send all sched.c modifications via the scheduler tree. Going via other trees is fine when there's agreement by the maintainers - but this is one of the rare cases where that's not the case. Ingo -- 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/
Powered by blists - more mailing lists