On Fri, Oct 19, 2018 at 10:32 AM, <valdis.kletnieks@xxxxxx> wrote: > On Wed, 17 Oct 2018 23:59:07 -0700, "Joel Fernandes (Google)" said: >> This usecase cannot be implemented with the existing F_SEAL_WRITE seal. >> To support the usecase, this patch adds a new F_SEAL_FUTURE_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: > > What is supposed to happen if some other process has an already existing R/W > mmap of the region? (For that matter, the test program doesn't seem to > actually test that the existing mmap region remains writable?) > Why would it not remain writable? We don't change anything in the mapping that prevents it from being writable, in the patch. We do test that existing writable mmaps can continue to exist after the seal is set, in a way, because we test that setting of the seal succeeds. I could test that processor stores can continue to happen my doing a memset into the existing map, but I feel that is like testing 2+2 = 4, in a way ;-) Do you really think its worth testing? If you do, then I could add a test for that. - Joel
