summaryrefslogtreecommitdiff
path: root/drivers/usb/musb/cppi_dma.h
diff options
context:
space:
mode:
authorYotam Gigi <yotamg@mellanox.com>2017-02-01 15:30:03 +0200
committerDavid S. Miller <davem@davemloft.net>2017-02-03 15:16:46 -0500
commit295a6e06d21e1f469c9f38b00125a13b60ad4e7c (patch)
tree56e1c64262e3ef4876e8d480555508d6a45358e7 /drivers/usb/musb/cppi_dma.h
parent1ce8460496c05379c66edc178c3c55ca4e953044 (diff)
net/sched: act_ife: Change to use ife module
Use the encode/decode functionality from the ife module instead of using implementation inside the act_ife. Reviewed-by: Jiri Pirko <jiri@mellanox.com> Signed-off-by: Yotam Gigi <yotamg@mellanox.com> Signed-off-by: Jamal Hadi Salim <jhs@mojatatu.com> Signed-off-by: Roman Mashak <mrv@mojatatu.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/usb/musb/cppi_dma.h')
0 files changed, 0 insertions, 0 deletions
st 121 == EREMOTEIO is what scsi_io_completion() asserts in case of invalid opcodes. Back to the original problem of userspace segfaults: this can be tracked down to ata_format_sct_write_same() overwriting the input page. Sometimes, this page is ZERO_PAGE(0) which ceases to be filled with zeros from that point on. Since ZERO_PAGE(0) is used for userspace .bss mappings, code of the following is doomed: static char *a = NULL; /* .bss */ ... if (a) *a = 'a'; This problem is not solved by disabling SCT Write Same for !ZAC devices only. It can certainly be fixed, but the final release is quite close -- so disable SCT Write Same for all ATA devices rather than introducing some SCT key buffer allocation schemes at this point. Fixes: 7b2030942859 ("libata: Add support for SCT Write Same") Signed-off-by: Nicolai Stange <nicstange@gmail.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/pmu-events/arch')