diff options
| author | David Herrmann <dh.herrmann@gmail.com> | 2014-08-18 23:54:10 +0200 |
|---|---|---|
| committer | David Herrmann <dh.herrmann@gmail.com> | 2014-08-18 23:56:36 +0200 |
| commit | 1ac36c67dd4d3fb5b73939293673fcd6debae699 (patch) | |
| tree | a97ea5e18b5b1e429951939dda7664bfc4bc6cc9 /test/f.service | |
| parent | 9da465df2a7d5d87e4af61364fb1475b1c8cbc6f (diff) | |
bus: map sealed memfds as MAP_PRIVATE
Mapping files as MAP_SHARED is handled by the kernel as 'writable'
mapping. Always! Even with PROT_READ. Reason for that is,
mprotect(PROT_WRITE) could change the mapping underneath and currently
there is no kernel infrastructure to add protection there. This might
change in the future, but until then, map sealed files as MAP_PRIVATE so
we don't get EPERM.
Diffstat (limited to 'test/f.service')
0 files changed, 0 insertions, 0 deletions