summaryrefslogtreecommitdiff
path: root/include/net/llc_s_ac.h
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2017-01-18 14:29:17 +0000
committerAl Viro <viro@zeniv.linux.org.uk>2017-01-31 13:23:09 -0500
commit62deb8187d116581c88c69a2dd9b5c16588545d4 (patch)
tree94e2822599e451d780de44f7c9d8b667accf44a9 /include/net/llc_s_ac.h
parent566cf877a1fcb6d6dc0126b076aad062054c2637 (diff)
FS-Cache: Initialise stores_lock in netfs cookie
Initialise the stores_lock in fscache netfs cookies. Technically, it shouldn't be necessary, since the netfs cookie is an index and stores no data, but initialising it anyway adds insignificant overhead. Signed-off-by: David Howells <dhowells@redhat.com> Reviewed-by: Jeff Layton <jlayton@redhat.com> Acked-by: Steve Dickson <steved@redhat.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'include/net/llc_s_ac.h')
0 files changed, 0 insertions, 0 deletions
t 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 'include/trace/events/mdio.h')