From: Jason Gunthorpe Subject: Re: [PATCH for-rc 6/7] IB/hfi1: Remove overly conservative VM_EXEC flag check Date: Fri, 18 Jan 2019 14:02:35 -0700 Message-ID: <20190118210235.GA20663@ziepe.ca> References: <20190117203920.30826.76720.stgit@scvm10.sc.intel.com> <20190117204159.30826.92063.stgit@scvm10.sc.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20190117204159.30826.92063.stgit@scvm10.sc.intel.com> Sender: stable-owner@vger.kernel.org To: Dennis Dalessandro Cc: dledford@redhat.com, linux-rdma@vger.kernel.org, "Michael J. Ruhl" , Mike Marciniszyn , Ira Weiny , stable@vger.kernel.org List-Id: linux-rdma@vger.kernel.org On Thu, Jan 17, 2019 at 12:42:04PM -0800, Dennis Dalessandro wrote: > From: Michael J. Ruhl > > Applications that use the stack for execution purposes cause > PSM jobs to fail during mmap(). > > Both Fortran (non-standard format parsing) and C (callback > functions located in the stack) applications can be written > such that stack execution is required. > > Because of this the EXECSTACK bit can be automatically set at link > time for any application. > > On application load, the ELF loader evaluates the EXECSTACK bit > for the application and it's linked libraries. It will set the > process VM flags to allow the stack to include the VM_EXEC bit > if the EXECSTACK bit is set. This flag is propagated to the > driver during the mmap() call in the vma flag bits. > > Checking for this bit and failing the request with EPERM is overly > conservative and will break any PSM application that has the bit set. > > Remove the VM_EXEC flag from the check. > > Cc: #v4.14+ > Fixes: 12220267645c ("IB/hfi: Protect against writable mmap") > Reviewed-by: Mike Marciniszyn > Reviewed-by: Dennis Dalessandro > Reviewed-by: Ira Weiny > Signed-off-by: Michael J. Ruhl > Signed-off-by: Dennis Dalessandro > --- > drivers/infiniband/hw/hfi1/file_ops.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) applied to for-next Thanks, Jason