Re: [PATCH 0/1] MR1003: gdiplus: Use atomic write for releasing GpImage lock.

[Esme Povirk (＠madewokherd)]

On Mon Oct 10 19:53:20 2022 +0000, Esme Povirk wrote:
> Would that just mean when we currently have a function that locks and
> calls another function that locks, we make a helper for the inner
> function that assumes the image is already locked?
> If we do recurse with an SRWLOCK, that'll hang, right?
> I think it's more work than necessary, but I'd be open to it, yes.

Actually, we don't want to ever block so I guess instead of hanging on recurse the function will just fail.