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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 18 May 2022 00:22:24 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Kees Cook <keescook@...omium.org> Cc: Christophe de Dinechin <dinechin@...hat.com>, Ingo Molnar <mingo@...hat.com>, Juri Lelli <juri.lelli@...hat.com>, Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, Daniel Bristot de Oliveira <bristot@...hat.com>, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH v3] sched/core: Address classes via __begin_sched_classes On Tue, May 17, 2022 at 10:35:44AM -0700, Kees Cook wrote: > What you've got below is almost exactly what I had in my first attempt > at this (that I never posted). What I was missing and couldn't track > down were the places you used sched_class_above(). I should have sent > _that_ patch and asked where the comparisons were that I couldn't find. > I think what you've got is much cleaner, as it makes the for loop use > the normal iterator idiom. Don't feel too bad; I forgot about the comparison in check_preempt_curr() myself and cursed a while trying to figure out why it stopped booting. Anyway; I suppose I'll go queue the thing in sched/core so we can forget about all this again.
Powered by blists - more mailing lists