summaryrefslogtreecommitdiff
path: root/fs/9p/acl.h
diff options
context:
space:
mode:
authorDimitris Michailidis <dmichail@google.com>2017-01-31 16:03:13 -0800
committerDavid S. Miller <davem@davemloft.net>2017-02-01 12:10:56 -0500
commit1a2a14444d32b89b28116daea86f63ced1716668 (patch)
treeff12c476ed162713c48f66d712375dc48955d6cb /fs/9p/acl.h
parentfd62d9f5c575f0792f150109f1fd24a0d4b3f854 (diff)
net: fix ndo_features_check/ndo_fix_features comment ordering
Commit cdba756f5803a2 ("net: move ndo_features_check() close to ndo_start_xmit()") inadvertently moved the doc comment for .ndo_fix_features instead of .ndo_features_check. Fix the comment ordering. Fixes: cdba756f5803a2 ("net: move ndo_features_check() close to ndo_start_xmit()") Signed-off-by: Dimitris Michailidis <dmichail@google.com> Acked-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/9p/acl.h')
0 files changed, 0 insertions, 0 deletions
eues 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/irda/ircomm/ircomm_ttp.c')