| 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: Sat, 25 Jul 2009 23:54:59 +0100 From: Jamie Lokier <jamie@...reable.org> To: Raistlin <raistlin@...ux.it> Cc: Peter Zijlstra <peterz@...radead.org>, sen wang <wangsen.linux@...il.com>, mingo@...e.hu, akpm@...ux-foundation.org, kernel@...ivas.org, npiggin@...e.de, arjan@...radead.org, linux-arm-kernel@...ts.arm.linux.org.uk, linux-kernel@...r.kernel.org, Tommaso Cucinotta <tommaso.cucinotta@...up.it> Subject: Re: report a bug about sched_rt Raistlin wrote: > > http://feanor.sssup.it/~faggioli/papers/OSPERT-2009-dlexception.pdf > > It is probably not always the best way of doing, but it's something we > think it could be useful somewhere. Therefore, we are still working on > it, e.g., improving timer resolution, adding the support for new > semantic and programming models, etc. Moreover, we are open to any > suggestion and contribution about this work, especially from the > community! The biggest weakness I see is if the application has a bug such as overwriting random memory or terminating the thread which is receiving timer signals, it can easily break the scheduling policy by accident. When the scheduling policy is implemented in the kernel, it can only be broken by system calls requesting a change of scheduling policy, which are relatively unlikely, and if necessary that can be completely prevented by security controls. -- Jamie -- 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