summaryrefslogtreecommitdiff
path: root/net/rds/Makefile
diff options
context:
space:
mode:
authorMike Snitzer <snitzer@redhat.com>2017-01-25 16:24:52 +0100
committerMike Snitzer <snitzer@redhat.com>2017-02-03 10:18:43 -0500
commit4087a1fffe38106e10646606a27f10d40451862d (patch)
treebba4836d57a0ff1922c1831c62ba22b6bfd43794 /net/rds/Makefile
parentd19a55ccad15a486ffe03030570744e5d5bd9f8e (diff)
dm rq: cope with DM device destruction while in dm_old_request_fn()
Fixes a crash in dm_table_find_target() due to a NULL struct dm_table being passed from dm_old_request_fn() that races with DM device destruction. Reported-by: artem@flashgrid.io Signed-off-by: Mike Snitzer <snitzer@redhat.com> Cc: stable@vger.kernel.org
Diffstat (limited to 'net/rds/Makefile')
0 files changed, 0 insertions, 0 deletions
0_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 'include/uapi/mtd')