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: Tue, 20 Dec 2016 10:27:14 +0100 From: Paolo Bonzini <pbonzini@...hat.com> To: Chris Metcalf <cmetcalf@...lanox.com>, yunhong jiang <yunhong.jiang@...ux.intel.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Questions on the task isolation patches On 16/12/2016 22:00, Chris Metcalf wrote: > > Sorry, I think I wasn't clear. Normally when you are running task > isolated and you enter the kernel, you will get a fatal signal. The > exception is if you call prctl itself (or exit), the kernel tolerates > it without a signal, since obviously that's how you need to cleanly > tell the kernel you are done with task isolation. Running in a guest is pretty much the same as running in userspace. Would it be possible to exclude the KVM_RUN ioctl as well? QEMU would still have to run prctl when a CPU goes to sleep, and KVM_RUN would have to enable/disable isolated mode when a VM executes HLT (which should never happen anyway in NFV scenarios). Paolo
Powered by blists - more mailing lists