gtp: add MAINTAINERS - net-next.git

diff options

author	Pablo Neira <pablo@netfilter.org>	2017-02-10 13:26:27 +0100
committer	David S. Miller <davem@davemloft.net>	2017-02-10 16:04:20 -0500
commit	bed45f79a2afc9d7c279b880dfcac8f27d513b50 (patch)
tree	d88160d5a9c725b829bf175aaea57822c50bf85c /net/irda/qos.c
parent	daa5fc711ee0fdbec8d55734d3975c17f2070b97 (diff)

gtp: add MAINTAINERS

Add maintainers for this tunnel driver. Include main osmocom.org mailist list too. Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org> Signed-off-by: David S. Miller <davem@davemloft.net>

Diffstat (limited to 'net/irda/qos.c')

0 files changed, 0 insertions, 0 deletions

lass='commit-subject'>Merge branch 'sparc64-non-resumable-user-error-recovery'

Liam R. Howlett says: ==================== sparc64: Recover from userspace non-resumable PIO & MEM errors A non-resumable error from userspace is able to cause a kernel panic or trap loop due to the setup and handling of the queued traps once in the kernel. This patch series addresses both of these issues. The queues are 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 'tools/perf/arch/arm64/include')


context:
space:
mode: