diff options
author | Jason Gunthorpe <jgg@mellanox.com> | 2018-07-26 06:40:17 +0300 |
---|---|---|
committer | Jason Gunthorpe <jgg@mellanox.com> | 2018-08-01 23:55:48 +0300 |
commit | bbd51e881ff05aa6dccda025e335438f3b3a1dba (patch) | |
tree | 719d347f1f7e3145abed708ca69a3db82366ee16 /block/blk-ioc.c | |
parent | cc2e14e68004e6dec70842f990085f67c1f6fec7 (diff) | |
download | linux-bbd51e881ff05aa6dccda025e335438f3b3a1dba.tar.xz |
IB/uverbs: Do not pass struct ib_device to the write based methods
This is a step to get rid of the global check for disassociation. In this
model, the ib_dev is not proven to be valid by the core code and cannot be
provided to the method. Instead, every method decides if it is able to
run after disassociation and obtains the ib_dev using one of three
different approaches:
- Call srcu_dereference on the udevice's ib_dev. As before, this means
the method cannot be called after disassociation begins.
(eg alloc ucontext)
- Retrieve the ib_dev from the ucontext, via ib_uverbs_get_ucontext()
- Retrieve the ib_dev from the uobject->object after checking
under SRCU if disassociation has started (eg uobj_get)
Largely, the code is all ready for this, the main work is to provide a
ib_dev after calling uobj_alloc(). The few other places simply use
ib_uverbs_get_ucontext() to get the ib_dev.
This flexibility will let the next patches allow destroy to operate
after disassociation.
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
Diffstat (limited to 'block/blk-ioc.c')
0 files changed, 0 insertions, 0 deletions