diff options
| author | Kees Cook <keescook@chromium.org> | 2016-01-20 15:00:45 -0800 |
|---|---|---|
| committer | Olav Haugan <ohaugan@codeaurora.org> | 2017-01-12 16:01:51 -0800 |
| commit | 22562e0cec02807a65ece6cacbdd9b8ee95e074e (patch) | |
| tree | 9f3e457e260f31e1d1511ff57bb0a4956b7f5bac /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 2dc96b1cbbdcf5aef3780696708012d55fec57f2 (diff) | |
sysctl: enable strict writes
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
Change-Id: Ibf8d46fa34fa9fd4df3527dc4dfc3e3d31b2f7e0
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>
Git-commit: 41662f5cc55335807d39404371cfcbb1909304c4
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions