# # RxRPC session sockets # config AF_RXRPC tristate "RxRPC session sockets" depends on INET select CRYPTO select KEYS help Say Y or M here to include support for RxRPC session sockets (just the transport part, not the presentation part: (un)marshalling is left to the application). These are used for AFS kernel filesystem and userspace utilities. This module at the moment only supports client operations and is currently incomplete. See Documentation/networking/rxrpc.txt. config AF_RXRPC_IPV6 bool "IPv6 support for RxRPC" depends on (IPV6 = m && AF_RXRPC = m) || (IPV6 = y && AF_RXRPC) help Say Y here to allow AF_RXRPC to use IPV6 UDP as well as IPV4 UDP as its network transport. config AF_RXRPC_INJECT_LOSS bool "Inject packet loss into RxRPC packet stream" depends on AF_RXRPC help Say Y here to inject packet loss by discarding some received and some transmitted packets. config AF_RXRPC_DEBUG bool "RxRPC dynamic debugging" depends on AF_RXRPC help Say Y here to make runtime controllable debugging messages appear. See Documentation/networking/rxrpc.txt. config RXKAD bool "RxRPC Kerberos security" depends on AF_RXRPC select CRYPTO select CRYPTO_MANAGER select CRYPTO_BLKCIPHER select CRYPTO_PCBC select CRYPTO_FCRYPT help Provide kerberos 4 and AFS kaserver security handling for AF_RXRPC through the use of the key retention service. See Documentation/networking/rxrpc.txt. s='sub right'>Tobias Klauser
summaryrefslogtreecommitdiff
path: root/net/ncsi/Kconfig
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-01-30 14:28:22 -0800
committerDavid S. Miller <davem@davemloft.net>2017-01-30 14:28:22 -0800
commit54791b276b4000b307339f269d3bf7db877d536f (patch)
tree1c2616bd373ce5ea28aac2a53e32f5b5834901ce /net/ncsi/Kconfig
parent5d0e7705774dd412a465896d08d59a81a345c1e4 (diff)
parent047487241ff59374fded8c477f21453681f5995c (diff)
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 'net/ncsi/Kconfig')