From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <20181005222820.GB13613@kroah.com> References: <20181005192727.167933-1-joel@joelfernandes.org> <20181005125339.f6febfd3fcfdc69c6f408c50@linux-foundation.org> <20181005211058.GA193964@joelaf.mtv.corp.google.com> <20181005222820.GB13613@kroah.com> From: Joel Fernandes Date: Fri, 5 Oct 2018 15:31:37 -0700 Message-ID: Subject: Re: [PATCH RFC] mm: Add an fs-write seal to memfd To: Greg KH Cc: Andrew Morton , LKML , kernel-team , John Reck , John Stultz , Todd Kjos , Al Viro , "J. Bruce Fields" , Jeff Layton , Khalid Aziz , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Mike Kravetz Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-mm@kvack.org List-ID: On Fri, Oct 5, 2018 at 3:28 PM, Greg KH wrote: > On Fri, Oct 05, 2018 at 02:10:58PM -0700, Joel Fernandes wrote: >> On Fri, Oct 05, 2018 at 12:53:39PM -0700, Andrew Morton wrote: >> > On Fri, 5 Oct 2018 12:27:27 -0700 "Joel Fernandes (Google)" wrote: >> > >> > > To support the usecase, this patch adds a new F_SEAL_FS_WRITE seal which >> > > prevents any future mmap and write syscalls from succeeding while >> > > keeping the existing mmap active. The following program shows the seal >> > > working in action: >> > >> > Please be prepared to create a manpage patch for this one. >> >> Sure, I will do that. thanks, > > And a test case to the in-kernel memfd tests would be appreciated. Sure, I will do add to those self-tests. thanks, - Joel