diff options
author | David Herrmann <dh.herrmann@gmail.com> | 2014-08-08 14:25:36 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-08-08 15:57:31 -0700 |
commit | 05f65b5c70909ef686f865f0a85406d74d75f70f (patch) | |
tree | 4d412f64bb993713d8896fc334db87f1d026d86c /scripts/Makefile | |
parent | 87b2d44026e0e315a7401551e95b189ac4b28217 (diff) | |
download | linux-05f65b5c70909ef686f865f0a85406d74d75f70f.tar.gz linux-05f65b5c70909ef686f865f0a85406d74d75f70f.tar.bz2 linux-05f65b5c70909ef686f865f0a85406d74d75f70f.zip |
shm: wait for pins to be released when sealing
If we set SEAL_WRITE on a file, we must make sure there cannot be any
ongoing write-operations on the file. For write() calls, we simply lock
the inode mutex, for mmap() we simply verify there're no writable
mappings. However, there might be pages pinned by AIO, Direct-IO and
similar operations via GUP. We must make sure those do not write to the
memfd file after we set SEAL_WRITE.
As there is no way to notify GUP users to drop pages or to wait for them
to be done, we implement the wait ourself: When setting SEAL_WRITE, we
check all pages for their ref-count. If it's bigger than 1, we know
there's some user of the page. We then mark the page and wait for up to
150ms for those ref-counts to be dropped. If the ref-counts are not
dropped in time, we refuse the seal operation.
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Acked-by: Hugh Dickins <hughd@google.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Ryan Lortie <desrt@desrt.ca>
Cc: Lennart Poettering <lennart@poettering.net>
Cc: Daniel Mack <zonque@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'scripts/Makefile')
0 files changed, 0 insertions, 0 deletions