From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 0/7 v3] tools/hotplug: systemd changes for 4.5 Date: Wed, 7 Jan 2015 09:56:20 -0500 Message-ID: <20150107145620.GF30457@l.oracle.com> References: <1418988333-5404-1-git-send-email-olaf@aepfle.de> <20141219191032.GB9213@laptop.dumpdata.com> <20141222080639.GA6139@aepfle.de> <20141231153106.GA2928@laptop.dumpdata.com> <20150105212206.GA3869@l.oracle.com> <20150107095306.GE12049@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20150107095306.GE12049@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: wei.liu2@citrix.com, ian.campbell@citrix.com, mcgrof@do-not-panic.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org, m.a.young@durham.ac.uk, anthony.perard@citrix.com List-Id: xen-devel@lists.xenproject.org On Wed, Jan 07, 2015 at 10:53:06AM +0100, Olaf Hering wrote: > On Mon, Jan 05, Konrad Rzeszutek Wilk wrote: > > > +Release Issues > > +============== > > + > > +While we did the utmost to get a release out, there are certain > > +fixes which were not complete on time. As such please reference this > > +section if you are running into trouble. > > + > > + * systemd not working with Fedora Core 20, 21 or later (systemctl > > + reports xenstore failing to start). > > + > > + Systemd support is now part of Xen source code. While utmost work has > > + been done to make the systemd files compatible across all the > > + distributions, there might issues when using systemd files from > > + Xen sources. The work-around is to define an mount entry in > > + /etc/fstab as follow: > > + > > + tmpfs /var/lib/xenstored tmpfs > > + mode=755,context="system_u:object_r:xenstored_var_lib_t:s0" 0 0 > > + > > + > > Shouldnt this go into a new SELinux section in the INSTALL file? It is going in the web-page for 'Release Issues' and such. > > Its my understanding that the reported SELinux failure is not only > related to the context= mount option, but also to the socket passing > from systemd. I couldn't spot any errors in SELinux for this. Perhaps I had misconfigured? > > > Olaf