linux-kernel - Re: [GIT PULL rcu/next] rcu commits for 2.6.40

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110516073928.GA23252@elte.hu>
Date:	Mon, 16 May 2011 09:39:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Yinghai Lu <yinghai@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL rcu/next] rcu commits for 2.6.40

* Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:

> > And the way you can prove that it is my code rather than the arch
> > code is to show that the warning happens on your system when the
> > irq_enter()/irq_exit() calls are perfectly nested.
> 
> So I took another look at the RCU debugfs stats you provided earlier,
> and realized that your system gets a lot more NMIs than do the ones
> that I have access to.  So as a diagnostic patch, I ifdefed out the
> body of rcu_nmi_enter() and rcu_nmi_exit().

Well, but the delays are occuring all the time (and it's bisectable) and NMIs 
are generally not deterministic.

I'd really suggest the creation of a revert + finegrained series on top of 
core/rcu which would IMHO help us narrow this down a lot more directly than 
jumping between the 'need_resched bug', 'nmi bug' and 'barrier bug' hypoteses.

( Btw., the bug still has the feeling of a need_resched/scheduling/timing 
  artifact to me, not barriers or NMI. )

Thanks,

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