From: Sander Eikelenboom <linux@eikelenboom.it>
To: Takashi Iwai <tiwai@suse.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Julia Lawall <julia.lawall@lip6.fr>,
<linux-sound@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Sound USB: Prevent printk ratelimiting from spamming kernel log while DEBUG not defined
Date: Fri, 2 May 2014 18:25:30 +0200 [thread overview]
Message-ID: <80394451.20140502182530@eikelenboom.it> (raw)
In-Reply-To: <s5hppjwqhuy.wl%tiwai@suse.de>
Friday, May 2, 2014, 6:13:09 PM, you wrote:
> At Fri, 2 May 2014 15:09:27 +0200,
> Sander Eikelenboom wrote:
>>
>> This (widely used) construction:
>>
>> if(printk_ratelimit())
>> dev_dbg()
>>
>> Causes the ratelimiting to spam the kernel log with the "callbacks suppressed"
>> message below, even while the dev_dbg it is supposed to rate limit wouldn't
>> print anything because DEBUG is not defined for this device.
>>
>> [ 533.803964] retire_playback_urb: 852 callbacks suppressed
>> [ 538.807930] retire_playback_urb: 852 callbacks suppressed
>> [ 543.811897] retire_playback_urb: 852 callbacks suppressed
>> [ 548.815745] retire_playback_urb: 852 callbacks suppressed
>> [ 553.819826] retire_playback_urb: 852 callbacks suppressed
>>
>> So use dev_dbg_ratelimited() instead of this construction.
>>
>> Signed-off-by: Sander Eikelenboom <linux@eikelenboom.it>
> Thanks, applied. This is a result of the recent rewrite to dev_dbg()
> from plain printk(), I suppose.
Yes that patch (https://lkml.org/lkml/2014/4/9/457) prevented spamming the kernel log when debugging was enabled ..
but now the rate limiting code starts spamming the kernel log instead :-)
I must say i wasn't very aware of that effect either and also used this construction on
debug patches.
> Takashi
>> ---
>> sound/usb/pcm.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/sound/usb/pcm.c b/sound/usb/pcm.c
>> index 131336d..c62a165 100644
>> --- a/sound/usb/pcm.c
>> +++ b/sound/usb/pcm.c
>> @@ -1501,9 +1501,8 @@ static void retire_playback_urb(struct snd_usb_substream *subs,
>> * The error should be lower than 2ms since the estimate relies
>> * on two reads of a counter updated every ms.
>> */
>> - if (printk_ratelimit() &&
>> - abs(est_delay - subs->last_delay) * 1000 > runtime->rate * 2)
>> - dev_dbg(&subs->dev->dev,
>> + if (abs(est_delay - subs->last_delay) * 1000 > runtime->rate * 2)
>> + dev_dbg_ratelimited(&subs->dev->dev,
>> "delay: estimated %d, actual %d\n",
>> est_delay, subs->last_delay);
>>
>> --
>> 1.7.10.4
>>
prev parent reply other threads:[~2014-05-02 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:09 [PATCH] Prevent printk ratelimiting from spamming kernel log while DEBUG not defined Sander Eikelenboom
2014-05-02 13:09 ` [PATCH] Sound USB: " Sander Eikelenboom
2014-05-02 16:13 ` Takashi Iwai
2014-05-02 16:25 ` Sander Eikelenboom [this message]
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=80394451.20140502182530@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=tiwai@suse.de \
/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