From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49198] glxinfo SIGSEGV in pthread_detach under radeon_drm_cs_destroy under dri2_destroy_context
Date: Tue, 22 May 2012 15:42:42 +0000 [thread overview]
Message-ID: <bug-49198-502-HD9Wm9TrT7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49198-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=49198
--- Comment #7 from Andre Heider <a.heider@gmail.com> 2012-05-22 08:42:42 PDT ---
Well, I just skimmed over the patch, so maybe I'm missing something, but what
I'm seeing is: 2 threads
a) runs radeon_drm_cs_destroy()
b) runs radeon_drm_cs_emit_ioctl()
When e.g. a context switch occurs on thread a) between 1) and 2) then thread b)
can run pipe_semaphore_signal(&cs->flush_completed) before a) runs
pipe_semaphore_wait(&cs->flush_completed).
The former will effectively be a noop since no other thread is waiting and the
latter will block forever.
No?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-05-22 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 22:56 [Bug 49198] New: glxinfo SIGSEGV in pthread_detach under radeon_drm_cs_destroy under dri2_destroy_context bugzilla-daemon
2012-04-28 6:23 ` [Bug 49198] " bugzilla-daemon
2012-05-22 9:50 ` bugzilla-daemon
2012-05-22 10:11 ` bugzilla-daemon
2012-05-22 10:26 ` bugzilla-daemon
2012-05-22 11:36 ` bugzilla-daemon
2012-05-22 14:44 ` bugzilla-daemon
2012-05-22 15:42 ` bugzilla-daemon [this message]
2012-05-22 15:46 ` bugzilla-daemon
2012-05-22 16:03 ` bugzilla-daemon
2012-09-19 10:20 ` bugzilla-daemon
2012-09-19 13:17 ` bugzilla-daemon
2012-09-19 21:20 ` bugzilla-daemon
2012-09-20 7:27 ` bugzilla-daemon
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=bug-49198-502-HD9Wm9TrT7@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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