Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6240
--- Additional Comments From [EMAIL PROTECTED] 2006-03-21 18:58 ---
The o
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=6240
--- Additional Comments From [EMAIL PROTECTED] 2006-03-21 18:23 ---
I bui
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=5450
[EMAIL PROTECTED] changed:
What|Removed |Added
--
I think that's what drm_lock.c:drm_notifier is for.. block_all_signals is
only used by the DRM from what I can see just for this reason..
Dave.
On Mon, 20 Mar 2006, Keith Whitwell wrote:
I believe that on Linux, there is actually some code in the kernel to put on
hold various sorts of signa
I believe that on Linux, there is actually some code in the kernel to
put on hold various sorts of signal-delivery when we hold the lock.
This went in around 2000/2001, and probably everybody has forgotten
about it since then. The effect is that a ^Z issued while the client
holds the lock will
