nvme-fc: use blk_rq_nr_phys_segments - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/net/ceph/ceph_common.c

diff options

author	Christoph Hellwig <hch@lst.de>	2017-01-19 16:55:57 +0100
committer	Sagi Grimberg <sagi@grimberg.me>	2017-01-26 17:49:14 +0200
commit	19e420bb4076ace670addc55300e3b8c4a02dfc6 (patch)
tree	ba40aad7ab4fb28c0eafd0ee84959589f444f58d /net/ceph/ceph_common.c
parent	748ff8408f8e208f279ba221e5c12612fbb4dddb (diff)

nvme-fc: use blk_rq_nr_phys_segments

Without this deallocate won't work properly due to the mismatch of the bio/request size and the actual payload size. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: James Smart <james.smart@broadcom.com> Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>

Diffstat (limited to 'net/ceph/ceph_common.c')

0 files changed, 0 insertions, 0 deletions

30->lock', whereas in the rest of the code `pch->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>

Diffstat (limited to 'net/bluetooth/rfcomm/sock.c')