linux-kernel - Re: [PATCH 0/7] KVM: Kernel-based Virtual Machine

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200610221947.21638.arnd@arndb.de>
Date:	Sun, 22 Oct 2006 19:47:21 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Avi Kivity <avi@...ranet.com>
Cc:	Muli Ben-Yehuda <muli@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Anthony Liguori <aliguori@...ibm.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 0/7] KVM: Kernel-based Virtual Machine

On Sunday 22 October 2006 19:41, Avi Kivity wrote:
> One last thing: permissions.  The /dev/kvm model allows permissions to
> be controlled using standard unix access methods.  How do you control
> access to spufs?

The mount point has permissions that you can set to allow read/write
access to users/groups. You can do that as a mount option or later
with chmod.

spu_create has an argument to specify the permissions for a new
object and follows the regular umask rules.

I also chose to allow users to set permissions on each file in order
to do cross-user IPC, but so far, nobody has used this to my knowledge.

	Arnd <><
-
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/