| 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, 02 Dec 2011 07:46:16 +0200 From: Sasha Levin <levinsasha928@...il.com> To: Takuya Yoshikawa <yoshikawa.takuya@....ntt.co.jp> Cc: linux-kernel@...r.kernel.org, Avi Kivity <avi@...hat.com>, Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org, Takuya Yoshikawa <takuya.yoshikawa@...il.com> Subject: Re: [PATCH] KVM: Veirfy memory slot only for readability On Fri, 2011-12-02 at 12:16 +0900, Takuya Yoshikawa wrote: > (2011/12/02 10:15), Takuya Yoshikawa wrote: > > (2011/12/02 4:42), Sasha Levin wrote: > >> It's enough for memory slot to be readable, as the comment above the check > >> states. > >> > >> A user should be able to create read-only memory slot. > > Note: at that time, it looked to me that the API did not allow me to know > which type was being registered. Which code exactly assumes that all memory slots are writable? > Do you want to create read only memory slots for kvm tool? What KVM tool currently does is copy the kernel into guest memory and run it from there. An idea raised recently was instead of copying it we should mmap it into the memory to reduce footprint. This is why I'm looking into adding a read only memory slot. The KVM code doesn't have to know it's read only. -- Sasha. -- 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