From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
Cc: Greg M Lee <Greg.Lee-CM8Ft84HMKulVyrhU4qvOw@public.gmane.org>,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Daniel J Walsh <dwalsh-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Karl MacMillan <kmacmill-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: strange error loading kvm module on latest FC6 kernel
Date: Thu, 08 Mar 2007 15:52:04 +0200 [thread overview]
Message-ID: <45F01504.5050403@qumranet.com> (raw)
In-Reply-To: <1173361148.10467.30.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
Stephen Smalley wrote:
>> I will add this fs to policy.
>>
>
> What are the protection requirements for it? What should be allowed to
> access it?
>
>
It's unmountable, so no one outside the kernel should be able to access it.
Within the kernel, if you have access to the /dev/kvm inode, you should
be able to access it.
2.6.22 may have an anonymous inode internal filesystem, which will
supercede kvmfs (and eventpollfs and friends)
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-08 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 4:28 strange error loading kvm module on latest FC6 kernel Greg M Lee
[not found] ` <1173241719.4317.5.camel-nqhUBgQlnDodtexkPab+ZEgmxNRb6L7S@public.gmane.org>
2007-03-07 7:00 ` Avi Kivity
[not found] ` <45EE62F6.3060300-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-07 8:42 ` Greg M Lee
2007-03-07 15:34 ` James Morris
2007-03-08 13:37 ` Daniel J Walsh
[not found] ` <1173361148.10467.30.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <1173361148.10467.30.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2007-03-08 13:52 ` Avi Kivity [this message]
2007-03-08 16:38 ` Daniel J Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45F01504.5050403@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=Greg.Lee-CM8Ft84HMKulVyrhU4qvOw@public.gmane.org \
--cc=dwalsh-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kmacmill-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox