From: Joe Perches <joe@perches.com>
To: Jiri Slaby <jslaby@suse.cz>, David Miller <davem@davemloft.net>,
saidone <saidone@saidone.org>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org, lwn@lwn.net
Subject: Re: Linux 2.6.32.43 (WARN_RATELIMIT)
Date: Wed, 13 Jul 2011 14:35:45 -0700 [thread overview]
Message-ID: <1310592945.1662.27.camel@Joe-Laptop> (raw)
In-Reply-To: <4E1E0E04.8030200@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Wed, 2011-07-13 at 23:28 +0200, Jiri Slaby wrote:
> Cced Joe.
Thanks Jiri.
I didn't submit this patch for stable.
I don't even try to track stable.
Saidone also notified me, I just replied to him
and cc'd stable. Perhaps I should have cc'd lkml
as well. Saidone's proposed patch is attached.
cheers, Joe
> On 07/13/2011 11:21 PM, Jiri Slaby wrote:
> > On 07/13/2011 11:16 PM, Jiri Slaby wrote:
> >> On 07/13/2011 05:45 AM, Greg KH wrote:
> >>> Joe Perches (2):
> >>> bug.h: Add WARN_RATELIMIT
> >>> net: filter: Use WARN_RATELIMIT
> >>
> >> Hi, this causes a build failure on PPC with minimalistic config (PS3) [1]:
> >> net/core/filter.c: In function 'sk_run_filter':
> >> net/core/filter.c:297: error: implicit declaration of function
> >> 'WARN_RATELIMIT'
> >>
> >> net/core/filter.c should include linux/bug.h (or linux/kernel.h).
> >
> > Ah, no, PS3 doesn't have CONFIG_BUG set.
>
> A fix attached. Upstream doesn't need it. There it is all in
> linux/ratelimit.h
>
> >> [1]
> >> http://gitorious.org/opensuse/kernel-source/blobs/SLE11-SP1/config/ppc/ps3
> >>
> >> regards,
[-- Attachment #2: Attached message - Re: WARN_RATELIMIT --]
[-- Type: message/rfc822, Size: 2352 bytes --]
From: saidone <saidone@saidone.org>
To: Joe Perches <joe@perches.com>
Cc: stable <stable@kernel.org>
Subject: Re: WARN_RATELIMIT
Date: Wed, 13 Jul 2011 19:44:46 +0200
Message-ID: <4E1DD98E.5030903@saidone.org>
Hi Joe, I found that the problem was that I have debugfs disabled (#
CONFIG_BUG is not set).
I cannot make better than this patch to net/core/filter.c:
#ifdef CONFIG_BUG
WARN_RATELIMIT(1, "Unknown code:%u jt:%u tf:%u
k:%u\n",
fentry->code, fentry->jt,
fentry->jf, fentry->k);
#endif
#ifndef CONFIG_BUG
WARN_ON(1);
#endif
return 0;
However, at least, it works ;-)
Thank you very much for the hints,
Marco Marini
On 13/07/2011 16:52, Joe Perches wrote:
> On Wed, 2011-07-13 at 12:37 +0200, saidone wrote:
>> Hello Joe,
>> I tried to build the latest stable kernel 2.6.32.43 with gcc 3.4.6, but
>> it stopped while compiling filter.c:
>> net/core/filter.c: In function `sk_run_filter':
>> net/core/filter.c:294: error: implicit declaration of function
>> `WARN_RATELIMIT'
>> How can I patch it in a "safe" manner?
>> Thanks in advance,
>> Marco Marini
>
> I believe net/core/filter.c will need to
>
> #include<linux/ratelimit.h>
prev parent reply other threads:[~2011-07-13 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 3:45 Linux 2.6.32.43 Greg KH
2011-07-13 3:46 ` Greg KH
2011-07-13 21:16 ` Jiri Slaby
2011-07-13 21:21 ` Jiri Slaby
2011-07-13 21:28 ` Jiri Slaby
2011-07-13 21:35 ` Joe Perches [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=1310592945.1662.27.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=saidone@saidone.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®