lakitu_defconfig: make /proc/self/mem read-write
The behavior was inherited from ChromeOS change (see [1], [2]). The
ChromeOS deicion to make the file read-only was based on the following
assumptions:
- There is no valid use case for the process to write to the /dev/self/mem
- The ptrace API that can be used to circumvent the limitation
also could be disabled system-wide because there was
These assumptions are not true for COS, since debugging is a valid use
case and therefor ptrace can't be disabled. Which removes a large share
of the value of having /dev/self/mem read-only.
In addition to this recent versions of gdb stopped working on COS
because gdb switched from using ptrace to directly modifying process
memory through the mem file. This is a significant user experience
regression.
Since there are more cons than pros to keeping the ChromeOS behavior
enabled, this commit reverts the access mode to default (r/w).
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=781376
[2] https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/753406
BUG=b/285213716
TEST=presubmit
RELEASE_NOTE=none
Change-Id: I8ddc7ed04ee5b26e0b6d43a3f790854d226f23d5
Reviewed-on: https://cos-review.googlesource.com/c/third_party/kernel/+/52034
Reviewed-by: Robert Kolchmeyer <rkolchmeyer@google.com>
Tested-by: Oleksandr Tymoshenko <ovt@google.com>
Reviewed-by: Vaibhav Rustagi <vaibhavrustagi@google.com>
2 files changed
