diff options
| author | Kees Cook <keescook@chromium.org> | 2016-01-21 02:00:45 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-07-05 15:35:14 +0300 |
| commit | fc7a4b8bbb8468ca980d72f7cbd47d90b0465136 (patch) | |
| tree | 7ed68295cfef7ab860b4cffec3695d664440a6e6 /mm | |
| parent | 9b8f56f595dea7ac3655dbf2318444e4749cfc65 (diff) | |
| download | linux-fc7a4b8bbb8468ca980d72f7cbd47d90b0465136.tar.xz | |
sysctl: enable strict writes
commit 41662f5cc55335807d39404371cfcbb1909304c4 upstream.
SYSCTL_WRITES_WARN was added in commit f4aacea2f5d1 ("sysctl: allow for
strict write position handling"), and released in v3.16 in August of
2014. Since then I can find only 1 instance of non-zero offset
writing[1], and it was fixed immediately in CRIU[2]. As such, it
appears safe to flip this to the strict state now.
[1] https://www.google.com/search?q="when%20file%20position%20was%20not%200"
[2] http://lists.openvz.org/pipermail/criu/2015-April/019819.html
Signed-off-by: Kees Cook <keescook@chromium.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sumit Semwal <sumit.semwal@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions