[PATCH] use printk_ratelimit() inside DRM_DEBUG

the DRM_DEBUG macro can be called within functions very oftenly
triggered, thus generating lots of message load and potentially
compromising system

Signed-off-by: Glauber de Oliveira Costa <[email protected]>

-- 
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"

--- linux-2.6.18.x86_64/drivers/char/drm/drmP.h.orig	2006-11-01 08:00:18.000000000 -0500
+++ linux-2.6.18.x86_64/drivers/char/drm/drmP.h	2006-11-01 08:06:27.000000000 -0500
@@ -185,7 +185,7 @@
 #if DRM_DEBUG_CODE
 #define DRM_DEBUG(fmt, arg...)						\
 	do {								\
-		if ( drm_debug )			\
+		if ( drm_debug && printk_ratelimit() )			\
 			printk(KERN_DEBUG				\
 			       "[" DRM_NAME ":%s] " fmt ,	\
 			       __FUNCTION__ , ##arg);			\

---

• Follow-Ups:
  • Re: [PATCH] use printk_ratelimit() inside DRM_DEBUG
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [PATCH 1/1] fat: improve sync performance by grouping writes revised
• Next by Date: Re: 2.6.19-rc <-> ThinkPads
• Previous by thread: [PATCH] swsusp: Use platform mode by default
• Next by thread: Re: [PATCH] use printk_ratelimit() inside DRM_DEBUG
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]