amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Nirmoy <nirmodas@amd.com>
To: amd-gfx@lists.freedesktop.org
Subject: Re: Mutex stays locked on error
Date: Tue, 23 Jun 2020 21:22:39 +0200	[thread overview]
Message-ID: <cd4d5837-9ab1-863c-01b5-ff139cd88cb9@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2006231945490.3391@kirika.lan>


[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]

Hi John,


The patch looks correct. Can you please send a proper patch

so that we can apply it.


Thanks,

Nirmoy

On 6/23/20 7:48 PM, John van der Kamp wrote:
> Hello,
>
> I was reading some code and came across this which looks like a mutex 
> not being unlocked when an error happens. I don't know what the code 
> does or how to test it, but it looks quite obvious. Patch is attached.
>
> John
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&amp;data=02%7C01%7Cnirmoy.das%40amd.com%7Ce8be7708d132495e63bf08d817a7ad86%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637285356777805685&amp;sdata=uG7iWdwahxHL06IJRPw7mnkH%2FifnTuYcxG%2BytRmnEZA%3D&amp;reserved=0

[-- Attachment #1.2: Type: text/html, Size: 1888 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2020-06-23 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 17:48 Mutex stays locked on error John van der Kamp
2020-06-23 19:22 ` Nirmoy [this message]
2020-06-23 20:38 John van der Kamp
2020-06-23 21:04 ` Alex Deucher

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=cd4d5837-9ab1-863c-01b5-ff139cd88cb9@amd.com \
    --to=nirmodas@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).