summaryrefslogtreecommitdiff
path: root/net/irda/irlmp_event.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-02-10 14:41:16 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-02-10 14:41:16 -0800
commita9dbf5c8d4c90f54777f89daf0e34d390808b672 (patch)
treea88262c9b95f6551d3d5baf89de0a9762e969253 /net/irda/irlmp_event.c
parentaca9fa0c8d225b1446dbed798b1d2f20e37e52cf (diff)
parent646ebd4166ca00bdf682a36bd2e1c9a74d848ac6 (diff)
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma
Pull rdma fixes from Doug Ledford: "Third round of -rc fixes for 4.10 kernel: - two security related issues in the rxe driver - one compile issue in the RDMA uapi header" * tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma: RDMA: Don't reference kernel private header from UAPI header IB/rxe: Fix mem_check_range integer overflow IB/rxe: Fix resid update
Diffstat (limited to 'net/irda/irlmp_event.c')
0 files changed, 0 insertions, 0 deletions
re fixed by simply zeroing the memory before use. PIO errors from userspace will result in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'sound/soc/codecs/cs42l42.h')