SELinux-Refpolicy Archive on
 help / color / Atom feed
From: Chris PeBenito <>
To: Russell Coker <>,
Subject: Re: virt_use_sysfs
Date: Sat, 18 Jul 2020 08:44:21 -0400
Message-ID: <> (raw)
In-Reply-To: <2061951.59CCVTTc8E@liv>

On 7/17/20 8:20 AM, Russell Coker wrote:
> Does it make sense to not have this enabled by default?  Getting meminfo from
> sysfs seems like a very reasonable and useful thing for a virtualisation
> system to do.  Not allowing that doesn't seem to give any benefit but does
> have potential for serious problems if things even work like that.

Perhaps the answer is to unconditionally allow reading of sysfs instead.  Then 
writes to sysfs would still be conditional and disabled by default.

Chris PeBenito

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 12:20 virt_use_sysfs Russell Coker
2020-07-18 12:44 ` Chris PeBenito [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

SELinux-Refpolicy Archive on

Archives are clonable:
	git clone --mirror selinux-refpolicy/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ \
	public-inbox-index selinux-refpolicy

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone