aboutsummaryrefslogtreecommitdiff
path: root/net/unix/unix_bpf.c
diff options
context:
space:
mode:
authorPavel Skripkin <[email protected]>2021-07-25 13:36:30 +0300
committerMarc Kleine-Budde <[email protected]>2021-07-30 08:47:01 +0200
commitfc43fb69a7af92839551f99c1a96a37b77b3ae7a (patch)
treeabc99b21de40cb49a69fbf239ea4fc60d76fa5e7 /net/unix/unix_bpf.c
parentf6b3c7848e66e9046c8a79a5b88fd03461cc252b (diff)
can: mcba_usb_start(): add missing urb->transfer_dma initialization
Yasushi reported, that his Microchip CAN Analyzer stopped working since commit 91c02557174b ("can: mcba_usb: fix memory leak in mcba_usb"). The problem was in missing urb->transfer_dma initialization. In my previous patch to this driver I refactored mcba_usb_start() code to avoid leaking usb coherent buffers. To archive it, I passed local stack variable to usb_alloc_coherent() and then saved it to private array to correctly free all coherent buffers on ->close() call. But I forgot to initialize urb->transfer_dma with variable passed to usb_alloc_coherent(). All of this was causing device to not work, since dma addr 0 is not valid and following log can be found on bug report page, which points exactly to problem described above. | DMAR: [DMA Write] Request device [00:14.0] PASID ffffffff fault addr 0 [fault reason 05] PTE Write access is not set Fixes: 91c02557174b ("can: mcba_usb: fix memory leak in mcba_usb") Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990850 Link: https://lore.kernel.org/r/[email protected] Cc: linux-stable <[email protected]> Reported-by: Yasushi SHOJI <[email protected]> Signed-off-by: Pavel Skripkin <[email protected]> Tested-by: Yasushi SHOJI <[email protected]> [mkl: fixed typos in commit message - thanks Yasushi SHOJI] Signed-off-by: Marc Kleine-Budde <[email protected]>
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions