From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
Cc: linux-rt-users@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Clark Williams <williams@redhat.com>
Subject: Re: [PATCH] net: iptables: rework the fix of xt_info locking
Date: Wed, 2 Mar 2011 21:58:53 +0100 [thread overview]
Message-ID: <20110302205853.GJ22310@pengutronix.de> (raw)
In-Reply-To: <20110302201414.GE8384@uudg.org>
On Wed, Mar 02, 2011 at 05:14:14PM -0300, Luis Claudio R. Goncalves wrote:
> Thomas,
>
> Maybe PREEMPT_NONE is not really what we want to check against, maybe it is
> RT_MUTEXES... anyway, this patch works fine as is in kernels with
> PREEMPT_NONE, PREEMPT_DESKTOP, PREEMPT_VOLUNTARY and PREEMPT_RT set.
>
> ---
>
> net: iptables: rework the fix of xt_info locking
>
> Commit 5bbbedc from tip/rt/2.6.33 fixed an annoying locking issue on
> PREEMPT_RT enabled kernels. I have observed a similar issue when testing a
> kernel with PREEMPT_DESKTOP enabled. My test kernels would boot fine and as
> soon as I tried to ssh into the test box I would see messages like this one:
>
> BUG: %Ps exited with wrong preemption count!
> => enter: 00000101, exit: 00000100.
> BUG: %Ps exited with wrong preemption count!
> => enter: 00000101, exit: 00000100.
> BUG: %Ps exited with wrong preemption count!
> => enter: 00000102, exit: 00000101.
This error message would be a bit more usful after this patch:
diff --git a/kernel/softirq.c b/kernel/softirq.c
index c35f72b..b3b20b0 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -335,8 +335,8 @@ debug_check_preempt_count_stop(__u32 *preempt_count, struct softirq_action *h)
if (*preempt_count == preempt_count())
return;
- print_symbol("BUG: %Ps exited with wrong preemption count!\n",
- (unsigned long)h->action);
+ printk("BUG: %ps exited with wrong preemption count!\n",
+ h->action);
printk("=> enter: %08x, exit: %08x.\n", *preempt_count, preempt_count());
preempt_count() = *preempt_count;
#endif
Note this is completely untested and applies on top of v2.6.33.7.2-rt30.
Thomas: should I send a proper patch or isn't it worth the effort?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-03-02 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 20:14 [PATCH] net: iptables: rework the fix of xt_info locking Luis Claudio R. Goncalves
2011-03-02 20:58 ` Uwe Kleine-König [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=20110302205853.GJ22310@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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).