Re: [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7

* Steven Rostedt <[email protected]> wrote:

> The code on line 133 is:
> 
> 	WARN_ON_ONCE(current->rcu_read_lock_nesting > NR_CPUS);
> 
> I have NR_CPUS set to 2 since the box I'm running this on only has 2 
> cpus and I see no reason to waste more data structures.
> 
> Is rcu read lock nesting deeper than 2?

ah, silly me - that should indeed be something fixed like 128.

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7
    • From: Steven Rostedt <[email protected]>
  • Re: [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7
    • From: Steven Rostedt <[email protected]>
  • Re: [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7
    • From: Ingo Molnar <[email protected]>
  • Re: [BUG RT] - rcupreempt.c:133 on 2.6.23-rc1-rt7
    • From: Steven Rostedt <[email protected]>

• Prev by Date: [PATCH] exit_notify: don't take tasklist for TIF_SIGPENDING re-targeting
• Next by Date: Re: [PATCH][RESEND] efficeon-agp leaks 'struct agp_bridge_data' in error paths of agp_efficeon_probe()
• Previous by thread: Re: [PATCH RT] put in a relatively high number for rcu read lock upper limit.
• Next by thread: [BUG RT] WARNING: at kernel/sched.c:5071 2.6.23-rc1-rt7
• 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]