Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org --- drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); } - return dma_fence_is_signaled(&fence->base); + return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->base.flags); }
static long
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->base.flags);
See the code above that:
if (fence->base.ops == &nouveau_fence_ops_legacy || fence->base.ops == &nouveau_fence_ops_uevent) { ....
Nouveau first tests if it's one of it's own fences, and if yes does some special handling. E.g. checking the fence status bits etc...
So this dma_fence_is_signaled() is for all non-nouveau fences and then not touching the internal flags is perfectly correct as far as I can see.
Regards, Christian.
} static long
On Thu, Apr 10, 2025 at 02:13:34PM +0200, Christian König wrote:
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->base.flags);
See the code above that:
if (fence->base.ops == &nouveau_fence_ops_legacy || fence->base.ops == &nouveau_fence_ops_uevent) {
I think this check is a bit pointless given that fence is already a struct nouveau_fence. :)
Am 10.04.25 um 14:21 schrieb Danilo Krummrich:
On Thu, Apr 10, 2025 at 02:13:34PM +0200, Christian König wrote:
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->base.flags);
See the code above that:
if (fence->base.ops == &nouveau_fence_ops_legacy || fence->base.ops == &nouveau_fence_ops_uevent) {
I think this check is a bit pointless given that fence is already a struct nouveau_fence. :)
Oh, good point. I totally missed that.
In this case that indeed doesn't make any sense at all.
(Unless somebody just blindly upcasted the structure, but I really hope that this isn't the case here).
Regards, Christian.
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Ah, I now got what you are trying to do here! But that won't help.
The problem is it is perfectly valid for somebody external (e.g. other driver, TTM etc...) to call dma_fence_is_signaled() on a nouveau fence.
This will then in turn still signal the fence and leave it on the pending list and creating the problem you have.
Regards, Christian.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->base.flags);
} static long
On Thu, 2025-04-10 at 14:58 +0200, Christian König wrote:
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Ah, I now got what you are trying to do here! But that won't help.
The problem is it is perfectly valid for somebody external (e.g. other driver, TTM etc...) to call dma_fence_is_signaled() on a nouveau fence.
This will then in turn still signal the fence and leave it on the pending list and creating the problem you have.
Good to hear – precisely that then is the use case for a dma_fence callback! ^_^ It guarantees that, no matter who signals a fence, no matter at what place, a certain action will always be performed.
I can't think of any other mechanism which could guarantee that a signaled fence immediately gets removed from nouveau's pending list, other than the callbacks.
But seriously, I don't think that anyone does this currently, nor do I think that anyone could get away with doing it without the entire computer burning down.
P.
Regards, Christian.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence-
base.flags);
} static long
Am 10.04.25 um 15:09 schrieb Philipp Stanner:
On Thu, 2025-04-10 at 14:58 +0200, Christian König wrote:
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Ah, I now got what you are trying to do here! But that won't help.
The problem is it is perfectly valid for somebody external (e.g. other driver, TTM etc...) to call dma_fence_is_signaled() on a nouveau fence.
This will then in turn still signal the fence and leave it on the pending list and creating the problem you have.
Good to hear – precisely that then is the use case for a dma_fence callback! ^_^ It guarantees that, no matter who signals a fence, no matter at what place, a certain action will always be performed.
I can't think of any other mechanism which could guarantee that a signaled fence immediately gets removed from nouveau's pending list, other than the callbacks.
But seriously, I don't think that anyone does this currently, nor do I think that anyone could get away with doing it without the entire computer burning down.
Yeah, I don't think that this is possible at the moment.
When you do stuff like that from the provider side you will always run into lifetime issues because in the signaling from interrupt case you then drop the last reference before the signaling is completed.
How about the attached (not even compile tested) patch? I think it should fix the issue.
Regards, Christian.
P.
Regards, Christian.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence-
base.flags);
} static long
On Thu, 2025-04-10 at 15:16 +0200, Christian König wrote:
Am 10.04.25 um 15:09 schrieb Philipp Stanner:
On Thu, 2025-04-10 at 14:58 +0200, Christian König wrote:
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Ah, I now got what you are trying to do here! But that won't help.
The problem is it is perfectly valid for somebody external (e.g. other driver, TTM etc...) to call dma_fence_is_signaled() on a nouveau fence.
This will then in turn still signal the fence and leave it on the pending list and creating the problem you have.
Good to hear – precisely that then is the use case for a dma_fence callback! ^_^ It guarantees that, no matter who signals a fence, no matter at what place, a certain action will always be performed.
I can't think of any other mechanism which could guarantee that a signaled fence immediately gets removed from nouveau's pending list, other than the callbacks.
But seriously, I don't think that anyone does this currently, nor do I think that anyone could get away with doing it without the entire computer burning down.
Yeah, I don't think that this is possible at the moment.
When you do stuff like that from the provider side you will always run into lifetime issues because in the signaling from interrupt case you then drop the last reference before the signaling is completed.
How about the attached (not even compile tested) patch? I think it should fix the issue.
This patch looked correct enough for me to try it out on top of my memleak fix series [1] (which seems to reveal all those problems through races appearing due to the removal of the waitqueue in nouveau_sched_fini()).
The code looked correct to me, but it still makes boom-boom, again because two parties get their fingers onto list_del():
[paste in case my editor explodes again: https://paste.debian.net/1368705/ ]
[ 41.681698] list_del corruption, ff31ae696cdc86a0->next is LIST_POISON1 (dead000000000100) [ 41.681720] ------------[ cut here ]------------ [ 41.681722] kernel BUG at lib/list_debug.c:56! [ 41.681729] Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [ 41.681732] CPU: 22 UID: 42 PID: 1733 Comm: gnome-shell Not tainted 6.14.0-rc4+ #11 [ 41.681735] Hardware name: Dell Inc. Precision 7960 Tower/01G0M6, BIOS 2.7.0 12/17/2024 [ 41.681737] RIP: 0010:__list_del_entry_valid_or_report+0x76/0xf0 [ 41.681743] Code: 75 66 5b b8 01 00 00 00 5d 41 5c c3 cc cc cc cc 48 89 ef e8 4c e7 b0 ff 48 89 ea 48 89 de 48 c7 c7 38 fb b5 a0 e8 3a 6d 6b ff <0f> 0b 4c 89 e7 e8 30 e7 b0 ff 4c 89 e2 48 89 de 48 c7 c7 70 fb b5 [ 41.681745] RSP: 0018:ff4fe30cc0f83b30 EFLAGS: 00010246 [ 41.681748] RAX: 000000000000004e RBX: ff31ae696cdc86a0 RCX: 0000000000000027 [ 41.681749] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff31ae8850321900 [ 41.681751] RBP: dead000000000100 R08: 0000000000000000 R09: 0000000000000000 [ 41.681752] R10: 7572726f63206c65 R11: 6c65645f7473696c R12: dead000000000122 [ 41.681753] R13: ff31ae696cdc8662 R14: ff4fe30cc0f83cb8 R15: 00007f68b7f9a000 [ 41.681754] FS: 00007f68bd0396c0(0000) GS:ff31ae8850300000(0000) knlGS:0000000000000000 [ 41.681756] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.681757] CR2: 00005577caaad68c CR3: 000000010407c003 CR4: 0000000000f71ef0 [ 41.681758] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.681759] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 41.681760] PKRU: 55555554 [ 41.681761] Call Trace: [ 41.681763] <TASK> [ 41.681764] ? __die_body.cold+0x19/0x27 [ 41.681768] ? die+0x2e/0x50 [ 41.681772] ? do_trap+0xca/0x110 [ 41.681775] ? do_error_trap+0x6a/0x90 [ 41.681776] ? __list_del_entry_valid_or_report+0x76/0xf0 [ 41.681778] ? exc_invalid_op+0x50/0x70 [ 41.681781] ? __list_del_entry_valid_or_report+0x76/0xf0 [ 41.681782] ? asm_exc_invalid_op+0x1a/0x20 [ 41.681788] ? __list_del_entry_valid_or_report+0x76/0xf0 [ 41.681789] nouveau_fence_is_signaled+0x47/0xc0 [nouveau] [ 41.681961] dma_resv_iter_walk_unlocked.part.0+0xbd/0x170 [ 41.681966] dma_resv_test_signaled+0x53/0x100 [ 41.681969] ttm_bo_release+0x12d/0x2f0 [ttm] [ 41.681979] nouveau_gem_object_del+0x54/0x80 [nouveau] [ 41.682090] ttm_bo_vm_close+0x41/0x60 [ttm] [ 41.682097] remove_vma+0x2c/0x70 [ 41.682100] vms_complete_munmap_vmas+0xd8/0x180 [ 41.682102] do_vmi_align_munmap+0x1d7/0x250 [ 41.682106] do_vmi_munmap+0xd0/0x170 [ 41.682109] __vm_munmap+0xb1/0x180 [ 41.682112] __x64_sys_munmap+0x1b/0x30 [ 41.682115] do_syscall_64+0x82/0x160 [ 41.682117] ? do_user_addr_fault+0x55a/0x7b0 [ 41.682121] ? exc_page_fault+0x7e/0x1a0 [ 41.682124] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 41.682127] RIP: 0033:0x7f68cceff02b [ 41.682130] Code: 73 01 c3 48 8b 0d e5 6d 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 6d 0f 00 f7 d8 64 89 01 48 [ 41.682131] RSP: 002b:00007ffed8d00c08 EFLAGS: 00000206 ORIG_RAX: 000000000000000b [ 41.682134] RAX: ffffffffffffffda RBX: 00005577ca99ef50 RCX: 00007f68cceff02b [ 41.682135] RDX: 0000000000000000 RSI: 0000000000001000 RDI: 00007f68b7f9a000 [ 41.682136] RBP: 00007ffed8d00c50 R08: 00005577cacc4160 R09: 00005577caccf930 [ 41.682137] R10: 000199999996d999 R11: 0000000000000206 R12: 0000000000000000 [ 41.682138] R13: 00007ffed8d00c60 R14: 00005577caf6c550 R15: 0000000000000035 [ 41.682141] </TASK> [ 41.682141] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill ip_set nf_tables qrtr sunrpc snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic snd_sof_pci snd_sof_xtensa_dsp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof snd_sof_utils snd_soc_acpi_intel_match snd_soc_acpi snd_soc_acpi_intel_sdca_quirks snd_sof_intel_hda_mlink snd_soc_sdca snd_soc_avs snd_ctl_led intel_rapl_msr snd_soc_hda_codec snd_hda_ext_core intel_rapl_common snd_hda_codec_realtek snd_soc_core intel_uncore_frequency snd_hda_codec_generic intel_uncore_frequency_common intel_ifs snd_hda_scodec_component snd_hda_codec_hdmi i10nm_edac snd_compress skx_edac_common binfmt_misc nfit snd_hda_intel snd_intel_dspcfg snd_hda_codec libnvdimm snd_hwdep snd_hda_core snd_seq snd_seq_device x86_pkg_temp_thermal dell_pc dell_wmi [ 41.682195] dax_hmem platform_profile intel_powerclamp sparse_keymap cxl_acpi snd_pcm cxl_port coretemp iTCO_wdt cxl_core spi_nor intel_pmc_bxt dell_wmi_sysman rapl pmt_telemetry dell_smbios iTCO_vendor_support pmt_class intel_cstate snd_timer vfat dcdbas isst_if_mmio mtd dell_smm_hwmon dell_wmi_ddv dell_wmi_descriptor intel_uncore firmware_attributes_class wmi_bmof atlantic fat einj pcspkr isst_if_mbox_pci snd isst_if_common intel_vsec i2c_i801 mei_me e1000e spi_intel_pci macsec soundcore i2c_smbus spi_intel mei joydev loop nfnetlink zram nouveau drm_ttm_helper ttm iaa_crypto polyval_clmulni rtsx_pci_sdmmc polyval_generic mmc_core gpu_sched ghash_clmulni_intel i2c_algo_bit nvme sha512_ssse3 drm_gpuvm drm_exec sha256_ssse3 idxd nvme_core sha1_ssse3 drm_display_helper rtsx_pci cec nvme_auth idxd_bus pinctrl_alderlake ip6_tables ip_tables fuse [ 41.682269] ---[ end trace 0000000000000000 ]--- [ 41.969442] RIP: 0010:__list_del_entry_valid_or_report+0x76/0xf0 [ 41.969458] Code: 75 66 5b b8 01 00 00 00 5d 41 5c c3 cc cc cc cc 48 89 ef e8 4c e7 b0 ff 48 89 ea 48 89 de 48 c7 c7 38 fb b5 a0 e8 3a 6d 6b ff <0f> 0b 4c 89 e7 e8 30 e7 b0 ff 4c 89 e2 48 89 de 48 c7 c7 70 fb b5 [ 41.969461] RSP: 0018:ff4fe30cc0f83b30 EFLAGS: 00010246 [ 41.969464] RAX: 000000000000004e RBX: ff31ae696cdc86a0 RCX: 0000000000000027 [ 41.969466] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff31ae8850321900 [ 41.969468] RBP: dead000000000100 R08: 0000000000000000 R09: 0000000000000000 [ 41.969469] R10: 7572726f63206c65 R11: 6c65645f7473696c R12: dead000000000122 [ 41.969470] R13: ff31ae696cdc8662 R14: ff4fe30cc0f83cb8 R15: 00007f68b7f9a000 [ 41.969471] FS: 00007f68bd0396c0(0000) GS:ff31ae8850300000(0000) knlGS:0000000000000000 [ 41.969473] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.969474] CR2: 00005577caaad68c CR3: 000000010407c003 CR4: 0000000000f71ef0 [ 41.969476] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.969477] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 41.969478] PKRU: 55555554
I fail to see why exactly right now, but am also quite tired. Might take another look the next days.
Although I'm not convinced that my solution is bad either. It's Nouveau, after all. On this ranch a cowboy has to defend himself with the pitchfork instead of the colt at times.
[1] https://lore.kernel.org/all/20250407152239.34429-2-phasta@kernel.org/
P.
Regards, Christian.
P.
Regards, Christian.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence-
base.flags);
} static long
On Thu, 2025-04-10 at 17:36 +0200, Philipp Stanner wrote:
On Thu, 2025-04-10 at 15:16 +0200, Christian König wrote:
Am 10.04.25 um 15:09 schrieb Philipp Stanner:
On Thu, 2025-04-10 at 14:58 +0200, Christian König wrote:
Am 10.04.25 um 11:24 schrieb Philipp Stanner:
Nouveau currently relies on the assumption that dma_fences will only ever get signaled through nouveau_fence_signal(), which takes care of removing a signaled fence from the list nouveau_fence_chan.pending.
This self-imposed rule is violated in nouveau_fence_done(), where dma_fence_is_signaled() (somewhat surprisingly, considering its name) can signal the fence without removing it from the list. This enables accesses to already signaled fences through the list, which is a bug.
In particular, it can race with nouveau_fence_context_kill(), which would then attempt to set an error code on an already signaled fence, which is illegal.
In nouveau_fence_done(), the call to nouveau_fence_update() already ensures to signal all ready fences. Thus, the signaling potentially performed by dma_fence_is_signaled() is actually not necessary.
Ah, I now got what you are trying to do here! But that won't help.
The problem is it is perfectly valid for somebody external (e.g. other driver, TTM etc...) to call dma_fence_is_signaled() on a nouveau fence.
This will then in turn still signal the fence and leave it on the pending list and creating the problem you have.
Good to hear – precisely that then is the use case for a dma_fence callback! ^_^ It guarantees that, no matter who signals a fence, no matter at what place, a certain action will always be performed.
I can't think of any other mechanism which could guarantee that a signaled fence immediately gets removed from nouveau's pending list, other than the callbacks.
But seriously, I don't think that anyone does this currently, nor do I think that anyone could get away with doing it without the entire computer burning down.
Yeah, I don't think that this is possible at the moment.
When you do stuff like that from the provider side you will always run into lifetime issues because in the signaling from interrupt case you then drop the last reference before the signaling is completed.
How about the attached (not even compile tested) patch? I think it should fix the issue.
This patch looked correct enough for me to try it out on top of my memleak fix series [1] (which seems to reveal all those problems through races appearing due to the removal of the waitqueue in nouveau_sched_fini()).
The code looked correct to me, but it still makes boom-boom, again because two parties get their fingers onto list_del():
[paste in case my editor explodes again: https://paste.debian.net/1368705/%C2%A0]
[ 41.681698] list_del corruption, ff31ae696cdc86a0->next is LIST_POISON1 (dead000000000100) [ 41.681720] ------------[ cut here ]------------ [ 41.681722] kernel BUG at lib/list_debug.c:56! [ 41.681729] Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [ 41.681732] CPU: 22 UID: 42 PID: 1733 Comm: gnome-shell Not tainted 6.14.0-rc4+ #11 [ 41.681735] Hardware name: Dell Inc. Precision 7960 Tower/01G0M6, BIOS 2.7.0 12/17/2024 [ 41.681737] RIP: 0010:__list_del_entry_valid_or_report+0x76/0xf0 [ 41.681743] Code: 75 66 5b b8 01 00 00 00 5d 41 5c c3 cc cc cc cc 48 89 ef e8 4c e7 b0 ff 48 89 ea 48 89 de 48 c7 c7 38 fb b5 a0 e8 3a 6d 6b ff <0f> 0b 4c 89 e7 e8 30 e7 b0 ff 4c 89 e2 48 89 de 48 c7 c7 70 fb b5 [ 41.681745] RSP: 0018:ff4fe30cc0f83b30 EFLAGS: 00010246 [ 41.681748] RAX: 000000000000004e RBX: ff31ae696cdc86a0 RCX: 0000000000000027 [ 41.681749] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff31ae8850321900 [ 41.681751] RBP: dead000000000100 R08: 0000000000000000 R09: 0000000000000000 [ 41.681752] R10: 7572726f63206c65 R11: 6c65645f7473696c R12: dead000000000122 [ 41.681753] R13: ff31ae696cdc8662 R14: ff4fe30cc0f83cb8 R15: 00007f68b7f9a000 [ 41.681754] FS: 00007f68bd0396c0(0000) GS:ff31ae8850300000(0000) knlGS:0000000000000000 [ 41.681756] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.681757] CR2: 00005577caaad68c CR3: 000000010407c003 CR4: 0000000000f71ef0 [ 41.681758] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.681759] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 41.681760] PKRU: 55555554 [ 41.681761] Call Trace: [ 41.681763] <TASK> [ 41.681764] ? __die_body.cold+0x19/0x27 [ 41.681768] ? die+0x2e/0x50 [ 41.681772] ? do_trap+0xca/0x110 [ 41.681775] ? do_error_trap+0x6a/0x90 [ 41.681776] ? __list_del_entry_valid_or_report+0x76/0xf0 [ 41.681778] ? exc_invalid_op+0x50/0x70 [ 41.681781] ? __list_del_entry_valid_or_report+0x76/0xf0 [ 41.681782] ? asm_exc_invalid_op+0x1a/0x20 [ 41.681788] ? __list_del_entry_valid_or_report+0x76/0xf0 [ 41.681789] nouveau_fence_is_signaled+0x47/0xc0 [nouveau] [ 41.681961] dma_resv_iter_walk_unlocked.part.0+0xbd/0x170 [ 41.681966] dma_resv_test_signaled+0x53/0x100 [ 41.681969] ttm_bo_release+0x12d/0x2f0 [ttm] [ 41.681979] nouveau_gem_object_del+0x54/0x80 [nouveau] [ 41.682090] ttm_bo_vm_close+0x41/0x60 [ttm] [ 41.682097] remove_vma+0x2c/0x70 [ 41.682100] vms_complete_munmap_vmas+0xd8/0x180 [ 41.682102] do_vmi_align_munmap+0x1d7/0x250 [ 41.682106] do_vmi_munmap+0xd0/0x170 [ 41.682109] __vm_munmap+0xb1/0x180 [ 41.682112] __x64_sys_munmap+0x1b/0x30 [ 41.682115] do_syscall_64+0x82/0x160 [ 41.682117] ? do_user_addr_fault+0x55a/0x7b0 [ 41.682121] ? exc_page_fault+0x7e/0x1a0 [ 41.682124] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 41.682127] RIP: 0033:0x7f68cceff02b [ 41.682130] Code: 73 01 c3 48 8b 0d e5 6d 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 0b 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 6d 0f 00 f7 d8 64 89 01 48 [ 41.682131] RSP: 002b:00007ffed8d00c08 EFLAGS: 00000206 ORIG_RAX: 000000000000000b [ 41.682134] RAX: ffffffffffffffda RBX: 00005577ca99ef50 RCX: 00007f68cceff02b [ 41.682135] RDX: 0000000000000000 RSI: 0000000000001000 RDI: 00007f68b7f9a000 [ 41.682136] RBP: 00007ffed8d00c50 R08: 00005577cacc4160 R09: 00005577caccf930 [ 41.682137] R10: 000199999996d999 R11: 0000000000000206 R12: 0000000000000000 [ 41.682138] R13: 00007ffed8d00c60 R14: 00005577caf6c550 R15: 0000000000000035 [ 41.682141] </TASK> [ 41.682141] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 rfkill ip_set nf_tables qrtr sunrpc snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic snd_sof_pci snd_sof_xtensa_dsp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof snd_sof_utils snd_soc_acpi_intel_match snd_soc_acpi snd_soc_acpi_intel_sdca_quirks snd_sof_intel_hda_mlink snd_soc_sdca snd_soc_avs snd_ctl_led intel_rapl_msr snd_soc_hda_codec snd_hda_ext_core intel_rapl_common snd_hda_codec_realtek snd_soc_core intel_uncore_frequency snd_hda_codec_generic intel_uncore_frequency_common intel_ifs snd_hda_scodec_component snd_hda_codec_hdmi i10nm_edac snd_compress skx_edac_common binfmt_misc nfit snd_hda_intel snd_intel_dspcfg snd_hda_codec libnvdimm snd_hwdep snd_hda_core snd_seq snd_seq_device x86_pkg_temp_thermal dell_pc dell_wmi [ 41.682195] dax_hmem platform_profile intel_powerclamp sparse_keymap cxl_acpi snd_pcm cxl_port coretemp iTCO_wdt cxl_core spi_nor intel_pmc_bxt dell_wmi_sysman rapl pmt_telemetry dell_smbios iTCO_vendor_support pmt_class intel_cstate snd_timer vfat dcdbas isst_if_mmio mtd dell_smm_hwmon dell_wmi_ddv dell_wmi_descriptor intel_uncore firmware_attributes_class wmi_bmof atlantic fat einj pcspkr isst_if_mbox_pci snd isst_if_common intel_vsec i2c_i801 mei_me e1000e spi_intel_pci macsec soundcore i2c_smbus spi_intel mei joydev loop nfnetlink zram nouveau drm_ttm_helper ttm iaa_crypto polyval_clmulni rtsx_pci_sdmmc polyval_generic mmc_core gpu_sched ghash_clmulni_intel i2c_algo_bit nvme sha512_ssse3 drm_gpuvm drm_exec sha256_ssse3 idxd nvme_core sha1_ssse3 drm_display_helper rtsx_pci cec nvme_auth idxd_bus pinctrl_alderlake ip6_tables ip_tables fuse [ 41.682269] ---[ end trace 0000000000000000 ]--- [ 41.969442] RIP: 0010:__list_del_entry_valid_or_report+0x76/0xf0 [ 41.969458] Code: 75 66 5b b8 01 00 00 00 5d 41 5c c3 cc cc cc cc 48 89 ef e8 4c e7 b0 ff 48 89 ea 48 89 de 48 c7 c7 38 fb b5 a0 e8 3a 6d 6b ff <0f> 0b 4c 89 e7 e8 30 e7 b0 ff 4c 89 e2 48 89 de 48 c7 c7 70 fb b5 [ 41.969461] RSP: 0018:ff4fe30cc0f83b30 EFLAGS: 00010246 [ 41.969464] RAX: 000000000000004e RBX: ff31ae696cdc86a0 RCX: 0000000000000027 [ 41.969466] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff31ae8850321900 [ 41.969468] RBP: dead000000000100 R08: 0000000000000000 R09: 0000000000000000 [ 41.969469] R10: 7572726f63206c65 R11: 6c65645f7473696c R12: dead000000000122 [ 41.969470] R13: ff31ae696cdc8662 R14: ff4fe30cc0f83cb8 R15: 00007f68b7f9a000 [ 41.969471] FS: 00007f68bd0396c0(0000) GS:ff31ae8850300000(0000) knlGS:0000000000000000 [ 41.969473] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 41.969474] CR2: 00005577caaad68c CR3: 000000010407c003 CR4: 0000000000f71ef0 [ 41.969476] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 41.969477] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 [ 41.969478] PKRU: 55555554
I fail to see why exactly right now, but am also quite tired. Might take another look the next days.
Although I'm not convinced that my solution is bad either. It's Nouveau, after all. On this ranch a cowboy has to defend himself with the pitchfork instead of the colt at times.
[1] https://lore.kernel.org/all/20250407152239.34429-2-phasta@kernel.org/
I think I see the issue now. Let's look at your code, Christian:
/* * In an ideal world, read would not assume the channel context is still alive. * This function may be called from another device, running into free memory as a * result. The drm node should still be there, so we can derive the index from * the fence context. */ static bool nouveau_fence_is_signaled(struct dma_fence *f) { struct nouveau_fence *fence = from_fence(f); struct nouveau_fence_chan *fctx = nouveau_fctx(fence); struct nouveau_channel *chan; bool ret = false;
rcu_read_lock(); chan = rcu_dereference(fence->channel); if (chan) ret = (int)(fctx->read(chan) - fence->base.seqno) >= 0; rcu_read_unlock();
if (ret) { /* * caller should have a reference on the fence, * else fence could get freed here */ WARN_ON(kref_read(&fence->base.refcount) <= 1);
list_del(&fence->head); dma_fence_put(&fence->base); }
return ret; }
[snip]
static const struct dma_fence_ops nouveau_fence_ops_uevent = { .get_driver_name = nouveau_fence_get_get_driver_name, .get_timeline_name = nouveau_fence_get_timeline_name, .enable_signaling = nouveau_fence_enable_signaling, .signaled = nouveau_fence_is_signaled, .release = nouveau_fence_release };
So the nouveau_fence_done() will run into nouveau_fence_is_signaled(). This will remove the list entry without any locking, because dma_fence_is_signaled() expects its callback to take the lock itself:
bool nouveau_fence_done(struct nouveau_fence *fence) { if (fence->base.ops == &nouveau_fence_ops_legacy || fence->base.ops == &nouveau_fence_ops_uevent) { struct nouveau_fence_chan *fctx = nouveau_fctx(fence); struct nouveau_channel *chan; unsigned long flags;
if (test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence-
base.flags))
return true;
spin_lock_irqsave(&fctx->lock, flags); chan = rcu_dereference_protected(fence->channel, lockdep_is_held(&fctx->lock)); if (chan && nouveau_fence_update(chan, fctx)) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); } return dma_fence_is_signaled(&fence->base); }
It could be, however, that at the same moment nouveau_fence_signal() is removing that entry, holding the appropriate lock.
So we have a race. Again.
You see, fixing things in Nouveau is difficult :) It gets more difficult if you want to clean it up "properly", so it conforms to rules such as those from dma_fence.
I have now provided two fixes that both work, but you are not satisfied with from the dma_fence-maintainer's perspective. I understand that, but please also understand that it's actually not my primary task to work on Nouveau. I just have to fix this bug to move on with my scheduler work.
So if you have another idea, feel free to share it. But I'd like to know how we can go on here.
I'm running out of ideas. What I'm wondering if we couldn't just remove performance hacky fastpath functions such as nouveau_fence_is_signaled() completely. It seems redundant to me.
Or we might add locking to it, but IDK what was achieved with RCU here. In any case it's definitely bad that Nouveau has so many redundant and half-redundant mechanisms.
P.
P.
Regards, Christian.
P.
Regards, Christian.
Replace the call to dma_fence_is_signaled() with nouveau_fence_base_is_signaled().
Cc: stable@vger.kernel.org # 4.10+, precise commit not to be determined Signed-off-by: Philipp Stanner phasta@kernel.org
drivers/gpu/drm/nouveau/nouveau_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c index 7cc84472cece..33535987d8ed 100644 --- a/drivers/gpu/drm/nouveau/nouveau_fence.c +++ b/drivers/gpu/drm/nouveau/nouveau_fence.c @@ -274,7 +274,7 @@ nouveau_fence_done(struct nouveau_fence *fence) nvif_event_block(&fctx->event); spin_unlock_irqrestore(&fctx->lock, flags); }
- return dma_fence_is_signaled(&fence->base);
- return test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence-
base.flags);
} static long
linux-stable-mirror@lists.linaro.org
-
Christian König -
Danilo Krummrich -
Philipp Stanner -
Philipp Stanner