summaryrefslogtreecommitdiff
path: root/tools/lib/subcmd/subcmd-config.c
diff options
context:
space:
mode:
authorDan Carpenter <dan.carpenter@oracle.com>2017-02-07 16:15:27 +0300
committerDavid S. Miller <davem@davemloft.net>2017-02-08 13:27:06 -0500
commitff4cf0e5ce952488074aa7f47734af1794f55fbc (patch)
treea8558eaf3e54f9a65ab9f11f5755c192883a01f0 /tools/lib/subcmd/subcmd-config.c
parent3efa70d78f218e4c9276b0bac0545e5184c1c47b (diff)
net: dsa: bcm_sf2: cleanup bcm_sf2_cfp_rule_get() a little
This patch doesn't affect how the code works. My static checker complains that the mask and shift doesn't make sense because 0xffffff << 16 goes beyond the end of 32 bits. It should be 0xffff instead but the existing code won't cause runtime bugs. Also the casting here is not needed and not consistent with the rest of the code. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/lib/subcmd/subcmd-config.c')
0 files changed, 0 insertions, 0 deletions
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 'drivers/usb/gadget/udc/bdc/Makefile')