From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422686AbWGNRmp (ORCPT ); Fri, 14 Jul 2006 13:42:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422682AbWGNRmp (ORCPT ); Fri, 14 Jul 2006 13:42:45 -0400 Received: from e2.ny.us.ibm.com ([32.97.182.142]:62142 "EHLO e2.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1422680AbWGNRmo (ORCPT ); Fri, 14 Jul 2006 13:42:44 -0400 Subject: Re: [RFC][PATCH 1/6] mprotect patch for use by SLIM From: Dave Hansen To: Kylene Jo Hall Cc: linux-kernel , LSM ML , Dave Safford , Mimi Zohar , Serge Hallyn In-Reply-To: <1152897868.23584.4.camel@localhost.localdomain> References: <1152897868.23584.4.camel@localhost.localdomain> Content-Type: text/plain Date: Fri, 14 Jul 2006 10:42:28 -0700 Message-Id: <1152898948.314.7.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2006-07-14 at 10:24 -0700, Kylene Jo Hall wrote: > This small patch makes mprotect available for use by SLIM for > write revocation. Hmmm. Do you really want mprotect() itself? Or, do you just want to keep people from writing? (there is a difference :) If somebody mmap()s something with write permissions, I would expect them to expect to see rw in /proc//maps. If you use mprotect() on that mmap() to remove the write permissions, the permissions will be reflected in /proc//maps. -- Dave