summaryrefslogtreecommitdiffstats
path: root/drivers/char/hpet.c
diff options
context:
space:
mode:
authorLogan Gunthorpe <logang@deltatee.com>2019-02-19 20:56:36 +0100
committerJon Mason <jdmason@kudzu.us>2019-06-13 14:58:12 +0200
commit51cb8dbf13246a0b144bff01d7d617efe550a055 (patch)
tree21287fecc3e86f22c6edc800102281d9d14377cc /drivers/char/hpet.c
parentNTB: ntb_hw_amd: set peer limit register (diff)
downloadlinux-51cb8dbf13246a0b144bff01d7d617efe550a055.tar.xz
linux-51cb8dbf13246a0b144bff01d7d617efe550a055.zip
NTB: ntb_transport: Ensure qp->tx_mw_dma_addr is initaliazed
Dan Carpenter's static checker reported: drivers/ntb/ntb_transport.c:1926 ntb_transport_create_queue() error: we previously assumed 'qp->tx_dma_chan' could be null (see line 1872) This is because the tx_mw_dma_addr is uninitialized in this function and may be incorrectly released using a NULL DMA channel. In practice this bug will not likely be seen. I'd guess you could hit this if you loaded ntb_netdev with use_dma=True, then unloaded it and loaded it again after setting the module parameter to use_dma=False. To fix this, we simply ensure that tx_mw_dma_addr is always initialized to zero. This is the safest in case any other part of the code operates on it if it is non-zero. Fixes: c59666bb32b9 ("NTB: ntb_transport: Ensure the destination buffer is mapped for TX DMA") Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Cc: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'drivers/char/hpet.c')
0 files changed, 0 insertions, 0 deletions