Re: Update setenforce, getenforce, sestatus man pages with references to each other.

2018-02-01 Thread Stephen Smalley
On Mon, 2018-01-29 at 11:27 -0600, Ben Kane wrote: > Hello, > > Last week I was studying for the RHCSE certification, and I couldn't > find how > to change SELinux's status from enforcing to permissive in the man > pages. This > patch updates the relevant man pages. > > - Switching emails > > I

Re: [PATCH] general protection fault in sock_has_perm

2018-02-01 Thread Greg KH
On Wed, Jan 31, 2018 at 04:06:37AM -0500, Paul Moore wrote: > On Tue, Jan 30, 2018 at 5:46 PM, Greg KH wrote: > > On Tue, Jan 30, 2018 at 11:00:04AM -0800, Mark Salyzyn wrote: > >> On 01/19/2018 09:41 AM, Stephen Smalley wrote: > >> > If we can't safely dereference the

Re: Update setenforce, getenforce, sestatus man pages with references to each other.

2018-02-01 Thread Stephen Smalley
On Thu, 2018-02-01 at 09:34 -0500, Stephen Smalley wrote: > On Mon, 2018-01-29 at 11:27 -0600, Ben Kane wrote: > > Hello, > > > > Last week I was studying for the RHCSE certification, and I > > couldn't > > find how > > to change SELinux's status from enforcing to permissive in the man > > pages.

Re: [PATCH v2] general protection fault in sock_has_perm

2018-02-01 Thread Mark Salyzyn
On 02/01/2018 09:02 AM, Stephen Smalley wrote: On Thu, 2018-02-01 at 08:20 -0800, Mark Salyzyn wrote: On 02/01/2018 08:00 AM, Paul Moore wrote: On Thu, Feb 1, 2018 at 10:37 AM, Mark Salyzyn wrote: In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket

Re: [PATCH v2 1/5] selinux:Remove direct references to policydb.

2018-02-01 Thread peter enderborg
On 01/30/2018 02:46 PM, Stephen Smalley wrote: > On Fri, 2018-01-26 at 15:32 +0100, peter.enderb...@sony.com wrote: >> From: Peter Enderborg >> >> To be able to use rcu locks we seed to address the policydb >> though a pointer. This preparation removes the export of the

Re: [PATCH v2 1/5] selinux:Remove direct references to policydb.

2018-02-01 Thread Stephen Smalley
On Thu, 2018-02-01 at 16:17 +0100, peter enderborg wrote: > On 01/30/2018 02:46 PM, Stephen Smalley wrote: > > On Fri, 2018-01-26 at 15:32 +0100, peter.enderb...@sony.com wrote: > > > From: Peter Enderborg > > > > > > To be able to use rcu locks we seed to address the

[PATCH v2] general protection fault in sock_has_perm

2018-02-01 Thread Mark Salyzyn
In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket flag") and all the associated infrastructure changes to take advantage of a RCU grace period before freeing, there is a heightened possibility that a security check is performed while an ill-timed setsockopt call races in from

Re: [PATCH v2] general protection fault in sock_has_perm

2018-02-01 Thread Stephen Smalley
On Thu, 2018-02-01 at 08:20 -0800, Mark Salyzyn wrote: > On 02/01/2018 08:00 AM, Paul Moore wrote: > > On Thu, Feb 1, 2018 at 10:37 AM, Mark Salyzyn > > wrote: > > > In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE > > > socket > > > flag") and all the

Re: [PATCH v2] general protection fault in sock_has_perm

2018-02-01 Thread Paul Moore
On Thu, Feb 1, 2018 at 11:20 AM, Mark Salyzyn wrote: > On 02/01/2018 08:00 AM, Paul Moore wrote: >> >> On Thu, Feb 1, 2018 at 10:37 AM, Mark Salyzyn wrote: >>> >>> In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket >>> flag") and all

Re: [PATCH v2] general protection fault in sock_has_perm

2018-02-01 Thread Greg KH
On Thu, Feb 01, 2018 at 08:20:13AM -0800, Mark Salyzyn wrote: > On 02/01/2018 08:00 AM, Paul Moore wrote: > > On Thu, Feb 1, 2018 at 10:37 AM, Mark Salyzyn wrote: > > > In the absence of commit a4298e4522d6 ("net: add SOCK_RCU_FREE socket > > > flag") and all the associated