From: John Zielinski <grim@undead.cc>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: radeon_pm.c locking problem
Date: Fri, 02 Jul 2004 13:29:38 -0400 [thread overview]
Message-ID: <40E59B82.7000807@undead.cc> (raw)
There's a post in the lkml from a Stanford researcher working on a tool
to sniff out locking problems. In his post he gave an example from the
radeon_pm.c file. Just want to make sure the appropriate people noticed
the post. It's subject is "[BUGS] [CHECKER] 99 synchronization bugs and
a lock summary database".
John
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-07-02 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 17:29 John Zielinski [this message]
2004-07-02 18:52 ` radeon_pm.c locking problem Kronos
2004-07-05 13:44 ` Benjamin Herrenschmidt
2004-07-05 16:41 ` Kronos
2004-07-05 21:24 ` David Eger
2004-07-05 22:03 ` Benjamin Herrenschmidt
2004-07-02 20:14 ` David Eger
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=40E59B82.7000807@undead.cc \
--to=grim@undead.cc \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).