From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com> To: "Christian König" <christian.koenig@amd.com>, "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: linaro-mm-sig@lists.linaro.org, matthew.auld@intel.com Subject: Re: [Intel-gfx] [RFC PATCH 1/2] dma-fence: Avoid establishing a locking order between fence classes Date: Tue, 30 Nov 2021 19:12:29 +0100 [thread overview] Message-ID: <712b54fa1c09ae5cc1d75739ad8a7286f1dae8db.camel@linux.intel.com> (raw) In-Reply-To: <250a8e47-2093-1a98-3859-0204ec4e60e6@amd.com> On Tue, 2021-11-30 at 16:02 +0100, Christian König wrote: > Am 30.11.21 um 15:35 schrieb Thomas Hellström: > > On Tue, 2021-11-30 at 14:26 +0100, Christian König wrote: > > > Am 30.11.21 um 13:56 schrieb Thomas Hellström: > > > > On 11/30/21 13:42, Christian König wrote: > > > > > Am 30.11.21 um 13:31 schrieb Thomas Hellström: > > > > > > [SNIP] > > > > > > > Other than that, I didn't investigate the nesting fails > > > > > > > enough to > > > > > > > say I can accurately review this. :) > > > > > > Basically the problem is that within enable_signaling() > > > > > > which > > > > > > is > > > > > > called with the dma_fence lock held, we take the dma_fence > > > > > > lock > > > > > > of > > > > > > another fence. If that other fence is a dma_fence_array, or > > > > > > a > > > > > > dma_fence_chain which in turn tries to lock a > > > > > > dma_fence_array > > > > > > we hit > > > > > > a splat. > > > > > Yeah, I already thought that you constructed something like > > > > > that. > > > > > > > > > > You get the splat because what you do here is illegal, you > > > > > can't > > > > > mix > > > > > dma_fence_array and dma_fence_chain like this or you can end > > > > > up > > > > > in a > > > > > stack corruption. > > > > Hmm. Ok, so what is the stack corruption, is it that the > > > > enable_signaling() will end up with endless recursion? If so, > > > > wouldn't > > > > it be more usable we break that recursion chain and allow a > > > > more > > > > general use? > > > The problem is that this is not easily possible for > > > dma_fence_array > > > containers. Just imagine that you drop the last reference to the > > > containing fences during dma_fence_array destruction if any of > > > the > > > contained fences is another container you can easily run into > > > recursion > > > and with that stack corruption. > > Indeed, that would require some deeper surgery. > > > > > That's one of the major reasons I came up with the > > > dma_fence_chain > > > container. This one you can chain any number of elements together > > > without running into any recursion. > > > > > > > Also what are the mixing rules between these? Never use a > > > > dma-fence-chain as one of the array fences and never use a > > > > dma-fence-array as a dma-fence-chain fence? > > > You can't add any other container to a dma_fence_array, neither > > > other > > > dma_fence_array instances nor dma_fence_chain instances. > > > > > > IIRC at least technically a dma_fence_chain can contain a > > > dma_fence_array if you absolutely need that, but Daniel, Jason > > > and I > > > already had the same discussion a while back and came to the > > > conclusion > > > to avoid that as well if possible. > > Yes, this is actually the use-case. But what I can't easily > > guarantee > > is that that dma_fence_chain isn't fed into a dma_fence_array > > somewhere > > else. How do you typically avoid that? > > > > Meanwhile I guess I need to take a different approach in the driver > > to > > avoid this altogether. > > Jason and I came up with a deep dive iterator for his use case, but I > think we don't want to use that any more after my dma_resv rework. > > In other words when you need to create a new dma_fence_array you > flatten > out the existing construct which is at worst case > dma_fence_chain->dma_fence_array->dma_fence. Ok, Are there any cross-driver contract here, Like every driver using a dma_fence_array need to check for dma_fence_chain and flatten like above? /Thomas > > Regards, > Christian. > > > > > /Thomas > > > > > > > Regards, > > > Christian. > > > > > > > /Thomas > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > Christian. > > > > > > > > > > > But I'll update the commit message with a typical splat. > > > > > > > > > > > > /Thomas > > >
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com> To: "Christian König" <christian.koenig@amd.com>, "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org Cc: linaro-mm-sig@lists.linaro.org, matthew.auld@intel.com Subject: Re: [RFC PATCH 1/2] dma-fence: Avoid establishing a locking order between fence classes Date: Tue, 30 Nov 2021 19:12:29 +0100 [thread overview] Message-ID: <712b54fa1c09ae5cc1d75739ad8a7286f1dae8db.camel@linux.intel.com> (raw) In-Reply-To: <250a8e47-2093-1a98-3859-0204ec4e60e6@amd.com> On Tue, 2021-11-30 at 16:02 +0100, Christian König wrote: > Am 30.11.21 um 15:35 schrieb Thomas Hellström: > > On Tue, 2021-11-30 at 14:26 +0100, Christian König wrote: > > > Am 30.11.21 um 13:56 schrieb Thomas Hellström: > > > > On 11/30/21 13:42, Christian König wrote: > > > > > Am 30.11.21 um 13:31 schrieb Thomas Hellström: > > > > > > [SNIP] > > > > > > > Other than that, I didn't investigate the nesting fails > > > > > > > enough to > > > > > > > say I can accurately review this. :) > > > > > > Basically the problem is that within enable_signaling() > > > > > > which > > > > > > is > > > > > > called with the dma_fence lock held, we take the dma_fence > > > > > > lock > > > > > > of > > > > > > another fence. If that other fence is a dma_fence_array, or > > > > > > a > > > > > > dma_fence_chain which in turn tries to lock a > > > > > > dma_fence_array > > > > > > we hit > > > > > > a splat. > > > > > Yeah, I already thought that you constructed something like > > > > > that. > > > > > > > > > > You get the splat because what you do here is illegal, you > > > > > can't > > > > > mix > > > > > dma_fence_array and dma_fence_chain like this or you can end > > > > > up > > > > > in a > > > > > stack corruption. > > > > Hmm. Ok, so what is the stack corruption, is it that the > > > > enable_signaling() will end up with endless recursion? If so, > > > > wouldn't > > > > it be more usable we break that recursion chain and allow a > > > > more > > > > general use? > > > The problem is that this is not easily possible for > > > dma_fence_array > > > containers. Just imagine that you drop the last reference to the > > > containing fences during dma_fence_array destruction if any of > > > the > > > contained fences is another container you can easily run into > > > recursion > > > and with that stack corruption. > > Indeed, that would require some deeper surgery. > > > > > That's one of the major reasons I came up with the > > > dma_fence_chain > > > container. This one you can chain any number of elements together > > > without running into any recursion. > > > > > > > Also what are the mixing rules between these? Never use a > > > > dma-fence-chain as one of the array fences and never use a > > > > dma-fence-array as a dma-fence-chain fence? > > > You can't add any other container to a dma_fence_array, neither > > > other > > > dma_fence_array instances nor dma_fence_chain instances. > > > > > > IIRC at least technically a dma_fence_chain can contain a > > > dma_fence_array if you absolutely need that, but Daniel, Jason > > > and I > > > already had the same discussion a while back and came to the > > > conclusion > > > to avoid that as well if possible. > > Yes, this is actually the use-case. But what I can't easily > > guarantee > > is that that dma_fence_chain isn't fed into a dma_fence_array > > somewhere > > else. How do you typically avoid that? > > > > Meanwhile I guess I need to take a different approach in the driver > > to > > avoid this altogether. > > Jason and I came up with a deep dive iterator for his use case, but I > think we don't want to use that any more after my dma_resv rework. > > In other words when you need to create a new dma_fence_array you > flatten > out the existing construct which is at worst case > dma_fence_chain->dma_fence_array->dma_fence. Ok, Are there any cross-driver contract here, Like every driver using a dma_fence_array need to check for dma_fence_chain and flatten like above? /Thomas > > Regards, > Christian. > > > > > /Thomas > > > > > > > Regards, > > > Christian. > > > > > > > /Thomas > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > Christian. > > > > > > > > > > > But I'll update the commit message with a typical splat. > > > > > > > > > > > > /Thomas > > >
next prev parent reply other threads:[~2021-11-30 18:28 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-30 12:19 [RFC PATCH 0/2] Attempt to avoid dma-fence-[chain|array] lockdep splats Thomas Hellström 2021-11-30 12:19 ` [Intel-gfx] " Thomas Hellström 2021-11-30 12:19 ` [RFC PATCH 1/2] dma-fence: Avoid establishing a locking order between fence classes Thomas Hellström 2021-11-30 12:19 ` [Intel-gfx] " Thomas Hellström 2021-11-30 12:25 ` Maarten Lankhorst 2021-11-30 12:25 ` [Intel-gfx] " Maarten Lankhorst 2021-11-30 12:31 ` Thomas Hellström 2021-11-30 12:31 ` [Intel-gfx] " Thomas Hellström 2021-11-30 12:42 ` Christian König 2021-11-30 12:42 ` [Intel-gfx] " Christian König 2021-11-30 12:56 ` Thomas Hellström 2021-11-30 12:56 ` [Intel-gfx] " Thomas Hellström 2021-11-30 13:26 ` Christian König 2021-11-30 13:26 ` [Intel-gfx] " Christian König 2021-11-30 14:35 ` Thomas Hellström 2021-11-30 14:35 ` [Intel-gfx] " Thomas Hellström 2021-11-30 15:02 ` Christian König 2021-11-30 15:02 ` [Intel-gfx] " Christian König 2021-11-30 18:12 ` Thomas Hellström [this message] 2021-11-30 18:12 ` Thomas Hellström 2021-11-30 19:27 ` Thomas Hellström 2021-11-30 19:27 ` [Intel-gfx] " Thomas Hellström 2021-12-01 7:05 ` Christian König 2021-12-01 7:05 ` [Intel-gfx] " Christian König 2021-12-01 8:23 ` [Linaro-mm-sig] " Thomas Hellström (Intel) 2021-12-01 8:23 ` [Intel-gfx] " Thomas Hellström (Intel) 2021-12-01 8:36 ` Christian König 2021-12-01 8:36 ` [Intel-gfx] " Christian König 2021-12-01 10:15 ` Thomas Hellström (Intel) 2021-12-01 10:15 ` [Intel-gfx] " Thomas Hellström (Intel) 2021-12-01 10:32 ` Christian König 2021-12-01 10:32 ` [Intel-gfx] " Christian König 2021-12-01 11:04 ` Thomas Hellström (Intel) 2021-12-01 11:04 ` [Intel-gfx] " Thomas Hellström (Intel) 2021-12-01 11:25 ` Christian König 2021-12-01 11:25 ` [Intel-gfx] " Christian König 2021-12-01 12:16 ` Thomas Hellström (Intel) 2021-12-01 12:16 ` Thomas Hellström (Intel) 2021-12-03 13:08 ` Christian König 2021-12-03 13:08 ` [Intel-gfx] " Christian König 2021-12-03 14:18 ` Thomas Hellström 2021-12-03 14:18 ` [Intel-gfx] " Thomas Hellström 2021-12-03 14:26 ` Christian König 2021-12-03 14:26 ` [Intel-gfx] " Christian König 2021-12-03 14:50 ` Thomas Hellström 2021-12-03 14:50 ` [Intel-gfx] " Thomas Hellström 2021-12-03 15:00 ` Christian König 2021-12-03 15:00 ` [Intel-gfx] " Christian König 2021-12-03 15:13 ` Thomas Hellström (Intel) 2021-12-03 15:13 ` [Intel-gfx] " Thomas Hellström (Intel) 2021-12-07 18:08 ` Daniel Vetter 2021-12-07 18:08 ` Daniel Vetter 2021-12-07 20:46 ` Thomas Hellström 2021-12-07 20:46 ` Thomas Hellström 2021-12-20 9:37 ` Daniel Vetter 2021-12-20 9:37 ` Daniel Vetter 2021-11-30 12:32 ` Thomas Hellström 2021-11-30 12:32 ` [Intel-gfx] " Thomas Hellström 2021-11-30 12:19 ` [RFC PATCH 2/2] dma-fence: Avoid excessive recursive fence locking from enable_signaling() callbacks Thomas Hellström 2021-11-30 12:19 ` [Intel-gfx] " Thomas Hellström 2021-11-30 12:36 ` [RFC PATCH 0/2] Attempt to avoid dma-fence-[chain|array] lockdep splats Christian König 2021-11-30 12:36 ` [Intel-gfx] " Christian König 2021-11-30 13:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork 2021-11-30 13:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2021-11-30 17:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=712b54fa1c09ae5cc1d75739ad8a7286f1dae8db.camel@linux.intel.com \ --to=thomas.hellstrom@linux.intel.com \ --cc=christian.koenig@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=linaro-mm-sig@lists.linaro.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=matthew.auld@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.