summaryrefslogtreecommitdiffstats
path: root/arch/riscv/include/uapi/asm/siginfo.h
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2018-09-25 12:04:47 +0200
committerEric W. Biederman <ebiederm@xmission.com>2018-10-03 16:46:28 +0200
commite75dc036c445b91b8b2ad4e6c9b05f04b6be6d3f (patch)
tree629998c30d946e656f969a40eeaca77da6249fbd /arch/riscv/include/uapi/asm/siginfo.h
parent018303a931a89b91dacd76140b8ebe51893dc5fe (diff)
downloadlinux-stable-e75dc036c445b91b8b2ad4e6c9b05f04b6be6d3f.tar.gz
linux-stable-e75dc036c445b91b8b2ad4e6c9b05f04b6be6d3f.tar.bz2
linux-stable-e75dc036c445b91b8b2ad4e6c9b05f04b6be6d3f.zip
signal: Fail sigqueueinfo if si_signo != sig
The kernel needs to validate that the contents of struct siginfo make sense as siginfo is copied into the kernel, so that the proper union members can be put in the appropriate locations. The field si_signo is a fundamental part of that validation. As such changing the contents of si_signo after the validation make no sense and can result in nonsense values in the kernel. As such simply fail if someone is silly enough to set si_signo out of sync with the signal number passed to sigqueueinfo. I don't expect a problem as glibc's sigqueue implementation sets "si_signo = sig" and CRIU just returns to the kernel what the kernel gave to it. If there is some application that calls sigqueueinfo directly that has a problem with this added sanity check we can revisit this when we see what kind of crazy that application is doing. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'arch/riscv/include/uapi/asm/siginfo.h')
0 files changed, 0 insertions, 0 deletions