From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <owner-linux-mm@kvack.org>
Date: Fri, 5 Oct 2018 12:53:39 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com, jreck@google.com,
 john.stultz@linaro.org, tkjos@google.com, gregkh@linuxfoundation.org, Al
 Viro <viro@zeniv.linux.org.uk>, "J. Bruce Fields" <bfields@fieldses.org>,
 Jeff Layton <jlayton@kernel.org>, Khalid Aziz <khalid.aziz@oracle.com>,
 linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Mike Kravetz
 <mike.kravetz@oracle.com>
Subject: Re: [PATCH RFC] mm: Add an fs-write seal to memfd
Message-Id: <20181005125339.f6febfd3fcfdc69c6f408c50@linux-foundation.org>
In-Reply-To: <20181005192727.167933-1-joel@joelfernandes.org>
References: <20181005192727.167933-1-joel@joelfernandes.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-linux-mm@kvack.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Fri,  5 Oct 2018 12:27:27 -0700 "Joel Fernandes (Google)" <joel@joelfernandes.org> 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.