diff options
| author | Christoph Hellwig <hch@lst.de> | 2019-07-24 09:52:55 +0300 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@mellanox.com> | 2019-07-25 22:14:40 +0300 |
| commit | de4ee728465f7c0c29241550e083139b2ce9159c (patch) | |
| tree | 73cc28b95ec232a4110fa216e5fc8a839c7c6581 /arch/nds32/include/uapi/asm/unistd.h | |
| parent | 5fbcf5015db8e9f04a9da6d40322622fa229da54 (diff) | |
| download | linux-de4ee728465f7c0c29241550e083139b2ce9159c.tar.xz | |
nouveau: unlock mmap_sem on all errors from nouveau_range_fault
Currently nouveau_svm_fault expects nouveau_range_fault to never unlock
mmap_sem, but the latter unlocks it for a random selection of error
codes. Fix this up by always unlocking mmap_sem for non-zero return values
in nouveau_range_fault, and only unlocking it in the caller for successful
returns.
Link: https://lore.kernel.org/r/20190724065258.16603-5-hch@lst.de
Tested-by: Ralph Campbell <rcampbell@nvidia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Jason Gunthorpe <jgg@mellanox.com>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
Diffstat (limited to 'arch/nds32/include/uapi/asm/unistd.h')
0 files changed, 0 insertions, 0 deletions