Displaying 20 results from an estimated 33 matches for "nouveau_gem_object_open".
2015 Nov 11
1
[PATCH] instmem/gk20a: fix race conditions
...gf100_vm_map_sg [nouveau]) from
[<bf0641b0>] (nvkm_vm_map+0x300/0x3bc [nouveau])
[ 270.567333] [<bf0641b0>] (nvkm_vm_map [nouveau]) from [<bf0bcbd4>]
(nouveau_bo_vma_add+0x74/0xa0 [nouveau])
[ 270.577189] [<bf0bcbd4>] (nouveau_bo_vma_add [nouveau]) from
[<bf0bdbd0>] (nouveau_gem_object_open+0x124/0x158 [nouveau])
[ 270.588196] [<bf0bdbd0>] (nouveau_gem_object_open [nouveau]) from
[<c02da62c>] (drm_gem_handle_create_tail+0x104/0x19c)
[ 270.599025] [<c02da62c>] (drm_gem_handle_create_tail) from
[<bf0be138>] (nouveau_gem_ioctl_new+0x90/0x18c [nouveau])
[ 270.60...
2019 May 17
4
drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
...m_ioctl+0xdf/0x177
[<000000000afc4996>] nvif_object_mthd+0xd4/0x100
[<000000002f7a7385>] nvif_vmm_map+0xeb/0x100
[<00000000ef2537ed>] nouveau_mem_map+0x79/0xd0
[<0000000014ddc0cf>] nouveau_vma_new+0x19d/0x1c0
[<00000000f99888a1>] nouveau_gem_object_open+0xd4/0x140
[<000000009cd25861>] drm_gem_handle_create_tail+0xe3/0x160
[<00000000191784d9>] nouveau_gem_ioctl_new+0x6e/0xd0
[<00000000159678df>] drm_ioctl_kernel+0x8c/0xd0
[<00000000fbaa6154>] drm_ioctl+0x1c4/0x360
[<000000006833fe15...
2020 Aug 13
0
[PATCH 09/20] drm/nouveau: Introduce GEM object functions
...pin,
- .gem_prime_get_sg_table = nouveau_gem_prime_get_sg_table,
.gem_prime_import_sg_table = nouveau_gem_prime_import_sg_table,
- .gem_prime_vmap = nouveau_gem_prime_vmap,
- .gem_prime_vunmap = nouveau_gem_prime_vunmap,
-
- .gem_free_object_unlocked = nouveau_gem_object_del,
- .gem_open_object = nouveau_gem_object_open,
- .gem_close_object = nouveau_gem_object_close,
.dumb_create = nouveau_display_dumb_create,
.dumb_map_offset = nouveau_display_dumb_map_offset,
diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c b/drivers/gpu/drm/nouveau/nouveau_gem.c
index 81f111ad3f4f..b04b8f6bb9d5 100644
--- a/drivers/gpu...
2020 Sep 15
0
[PATCH v2 09/21] drm/nouveau: Introduce GEM object functions
...pin,
- .gem_prime_get_sg_table = nouveau_gem_prime_get_sg_table,
.gem_prime_import_sg_table = nouveau_gem_prime_import_sg_table,
- .gem_prime_vmap = nouveau_gem_prime_vmap,
- .gem_prime_vunmap = nouveau_gem_prime_vunmap,
-
- .gem_free_object_unlocked = nouveau_gem_object_del,
- .gem_open_object = nouveau_gem_object_open,
- .gem_close_object = nouveau_gem_object_close,
.dumb_create = nouveau_display_dumb_create,
.dumb_map_offset = nouveau_display_dumb_map_offset,
diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c b/drivers/gpu/drm/nouveau/nouveau_gem.c
index 89adadf4706b..28e0cbb00876 100644
--- a/drivers/gpu...
2014 May 17
1
Machine freeze on latest Linus kernel, seems related to nouveau
...veau]
[235255.701457] [<ffffffffa02442c6>] nouveau_object_ctor+0x32/0xaf [nouveau]
[235255.701475] [<ffffffffa02430d1>] nouveau_gpuobj_new+0x4e/0x50 [nouveau]
[235255.701504] [<ffffffffa026d823>] nouveau_vm_get+0x151/0x27a [nouveau]
[235255.701545] [<ffffffffa02a3f47>] ?
nouveau_gem_object_open+0x7a/0xbe [nouveau]
[235255.701585] [<ffffffffa02a377d>] nouveau_bo_vma_add+0x36/0x9f [nouveau]
[235255.701624] [<ffffffffa02a3f61>]
nouveau_gem_object_open+0x94/0xbe [nouveau]
[235255.701640] [<ffffffffa007fb47>]
drm_gem_handle_create_tail+0xe0/0x106 [drm]
[235255.701654] [&l...
2023 Feb 14
3
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...seems like it could have a potential security
issue without this change.
A couple drivers like qxl_gem_object_open and vmw_gem_object_open
implement no-op hooks so no impact for them.
A bunch of other require a deeper look by individual owners to asses for
impact. Those are lima_gem_object_open, nouveau_gem_object_open,
panfrost_gem_open, radeon_gem_object_open and virtio_gpu_gem_object_open.
Putting aside the risk assesment of the above, some common scenarios to
think about are along these lines:
1)
Userspace closes a handle by speculatively "guessing" it from a second
thread.
This results in an unr...
2023 Feb 14
3
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...seems like it could have a potential security
issue without this change.
A couple drivers like qxl_gem_object_open and vmw_gem_object_open
implement no-op hooks so no impact for them.
A bunch of other require a deeper look by individual owners to asses for
impact. Those are lima_gem_object_open, nouveau_gem_object_open,
panfrost_gem_open, radeon_gem_object_open and virtio_gpu_gem_object_open.
Putting aside the risk assesment of the above, some common scenarios to
think about are along these lines:
1)
Userspace closes a handle by speculatively "guessing" it from a second
thread.
This results in an unr...
2023 Feb 20
2
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...without this change.
>>
>> A couple drivers like qxl_gem_object_open and vmw_gem_object_open
>> implement no-op hooks so no impact for them.
>>
>> A bunch of other require a deeper look by individual owners to asses for
>> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
>> panfrost_gem_open, radeon_gem_object_open and virtio_gpu_gem_object_open.
>>
>> Putting aside the risk assesment of the above, some common scenarios to
>> think about are along these lines:
>>
>> 1)
>> Userspace closes a handle by speculatively "gu...
2023 Feb 20
2
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...without this change.
>>
>> A couple drivers like qxl_gem_object_open and vmw_gem_object_open
>> implement no-op hooks so no impact for them.
>>
>> A bunch of other require a deeper look by individual owners to asses for
>> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
>> panfrost_gem_open, radeon_gem_object_open and virtio_gpu_gem_object_open.
>>
>> Putting aside the risk assesment of the above, some common scenarios to
>> think about are along these lines:
>>
>> 1)
>> Userspace closes a handle by speculatively "gu...
2015 Nov 09
2
[PATCH] instmem/gk20a: fix race conditions
The LRU list used for recycling CPU mappings was handling concurrency
very poorly. For instance, if an instobj was acquired twice before being
released once, it would end up into the LRU list even though there is
still a client accessing it.
This patch fixes this by properly counting how many clients are
currently using a given instobj.
While at it, we also raise errors when inconsistencies are
2019 May 17
0
drm/nouveau/core/memory: kmemleak 684 new suspected memory leaks
...[<000000000afc4996>] nvif_object_mthd+0xd4/0x100
> [<000000002f7a7385>] nvif_vmm_map+0xeb/0x100
> [<00000000ef2537ed>] nouveau_mem_map+0x79/0xd0
> [<0000000014ddc0cf>] nouveau_vma_new+0x19d/0x1c0
> [<00000000f99888a1>] nouveau_gem_object_open+0xd4/0x140
> [<000000009cd25861>] drm_gem_handle_create_tail+0xe3/0x160
> [<00000000191784d9>] nouveau_gem_ioctl_new+0x6e/0xd0
> [<00000000159678df>] drm_ioctl_kernel+0x8c/0xd0
> [<00000000fbaa6154>] drm_ioctl+0x1c4/0x360
>...
2020 May 20
0
[PATCH] drm/nouveau: fix runtime pm imbalance on error
...m.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c b/drivers/gpu/drm/nouveau/nouveau_gem.c
index f5ece1f94973..6697f960dd89 100644
--- a/drivers/gpu/drm/nouveau/nouveau_gem.c
+++ b/drivers/gpu/drm/nouveau/nouveau_gem.c
@@ -76,8 +76,10 @@ nouveau_gem_object_open(struct drm_gem_object *gem, struct drm_file *file_priv)
return ret;
ret = pm_runtime_get_sync(dev);
- if (ret < 0 && ret != -EACCES)
+ if (ret < 0 && ret != -EACCES) {
+ pm_runtime_put_autosuspend(dev);
goto out;
+ }
ret = nouveau_vma_new(nvbo, vmm, &vma);...
2023 Feb 20
1
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...rivers like qxl_gem_object_open and vmw_gem_object_open
>>>> implement no-op hooks so no impact for them.
>>>>
>>>> A bunch of other require a deeper look by individual owners to asses
>>>> for
>>>> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
>>>> panfrost_gem_open, radeon_gem_object_open and
>>>> virtio_gpu_gem_object_open.
>>>>
>>>> Putting aside the risk assesment of the above, some common scenarios to
>>>> think about are along these lines:
>>>>
>>>&g...
2023 Feb 20
1
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...rivers like qxl_gem_object_open and vmw_gem_object_open
>>>> implement no-op hooks so no impact for them.
>>>>
>>>> A bunch of other require a deeper look by individual owners to asses
>>>> for
>>>> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
>>>> panfrost_gem_open, radeon_gem_object_open and
>>>> virtio_gpu_gem_object_open.
>>>>
>>>> Putting aside the risk assesment of the above, some common scenarios to
>>>> think about are along these lines:
>>>>
>>>&g...
2015 Jun 15
4
[PATCH v2 0/2] drm/nouveau: option for staging ioctls and new GEM_SET_TILING ioctl
Second version of this patchset addressing Ben's comments and fixing a few
extra things.
This patchset proposes to introduce a "staging" module option to dynamically
enable features (mostly ioctls) that are merged but may be refined before
they are declared "stable". The second patch illustrates the use of this
staging option with the SET_TILING ioctl, which can be used to
2016 Apr 15
0
[Bug 82714] [G84] nouveau fails to properly initialize GPU
...00/0x110 [nouveau]
[ 578.943178] [<ffffffffa06355eb>] nvkm_vm_map+0x2fb/0x3b0 [nouveau]
[ 578.943186] [<ffffffffa0635d76>] ? nvkm_vm_get+0x1d6/0x260 [nouveau]
[ 578.943195] [<ffffffffa0692eee>] nouveau_bo_vma_add+0x5e/0x90 [nouveau]
[ 578.943203] [<ffffffffa069345a>] nouveau_gem_object_open+0x15a/0x190
[nouveau]
[ 578.943207] [<ffffffffa04000b9>] drm_gem_handle_create_tail+0xe9/0x1b0
[drm]
[ 578.943210] [<ffffffffa04001b5>] drm_gem_handle_create+0x35/0x40 [drm]
[ 578.943218] [<ffffffffa0693882>] nouveau_gem_ioctl_new+0xc2/0x1d0 [nouveau]
[ 578.943221] [<ff...
2023 Feb 14
0
[PATCH] drm/gem: Expose the buffer object handle to userspace last
...tial security
> issue without this change.
>
> A couple drivers like qxl_gem_object_open and vmw_gem_object_open
> implement no-op hooks so no impact for them.
>
> A bunch of other require a deeper look by individual owners to asses for
> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
> panfrost_gem_open, radeon_gem_object_open and virtio_gpu_gem_object_open.
>
> Putting aside the risk assesment of the above, some common scenarios to
> think about are along these lines:
>
> 1)
> Userspace closes a handle by speculatively "guessing" it from a secon...
2023 Feb 14
0
[Nouveau] [PATCH] drm/gem: Expose the buffer object handle to userspace last
...tial security
> issue without this change.
>
> A couple drivers like qxl_gem_object_open and vmw_gem_object_open
> implement no-op hooks so no impact for them.
>
> A bunch of other require a deeper look by individual owners to asses for
> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
> panfrost_gem_open, radeon_gem_object_open and virtio_gpu_gem_object_open.
>
> Putting aside the risk assesment of the above, some common scenarios to
> think about are along these lines:
>
> 1)
> Userspace closes a handle by speculatively "guessing" it from a secon...
2023 Feb 20
0
[Nouveau] [PATCH] drm/gem: Expose the buffer object handle to userspace last
...;>> A couple drivers like qxl_gem_object_open and vmw_gem_object_open
>>> implement no-op hooks so no impact for them.
>>>
>>> A bunch of other require a deeper look by individual owners to asses
>>> for
>>> impact. Those are lima_gem_object_open, nouveau_gem_object_open,
>>> panfrost_gem_open, radeon_gem_object_open and
>>> virtio_gpu_gem_object_open.
>>>
>>> Putting aside the risk assesment of the above, some common scenarios to
>>> think about are along these lines:
>>>
>>> 1)
>>> Userspace...
2014 Sep 26
0
[RFC PATCH 6/7] drm/nouveau: Support marking buffers for explicit sync
...au_gem.c */
extern int nouveau_gem_new(struct drm_device *, int size, int align,
uint32_t domain, uint32_t tile_mode,
- uint32_t tile_flags, struct nouveau_bo **);
+ uint32_t bo_flags, struct nouveau_bo **);
extern void nouveau_gem_object_del(struct drm_gem_object *);
extern int nouveau_gem_object_open(struct drm_gem_object *, struct drm_file *);
extern void nouveau_gem_object_close(struct drm_gem_object *,
@@ -35,6 +35,8 @@ extern int nouveau_gem_ioctl_cpu_fini(struct drm_device *, void *,
struct drm_file *);
extern int nouveau_gem_ioctl_info(struct drm_device *, void *,
stru...