[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181005125339.f6febfd3fcfdc69c6f408c50@linux-foundation.org>
Date: Fri, 5 Oct 2018 12:53:39 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Joel Fernandes (Google)" <joel@...lfernandes.org>
Cc: linux-kernel@...r.kernel.org, kernel-team@...roid.com,
jreck@...gle.com, john.stultz@...aro.org, tkjos@...gle.com,
gregkh@...uxfoundation.org, Al Viro <viro@...iv.linux.org.uk>,
"J. Bruce Fields" <bfields@...ldses.org>,
Jeff Layton <jlayton@...nel.org>,
Khalid Aziz <khalid.aziz@...cle.com>,
linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
Mike Kravetz <mike.kravetz@...cle.com>
Subject: Re: [PATCH RFC] mm: Add an fs-write seal to memfd
On Fri, 5 Oct 2018 12:27:27 -0700 "Joel Fernandes (Google)" <joel@...lfernandes.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.
Powered by blists - more mailing lists