linux-kernel - Re: rcu: endless stalls

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: <1339571575.7472.78.camel@marge.simpson.net>
Date:	Wed, 13 Jun 2012 09:12:55 +0200
From:	Mike Galbraith <efault@....de>
To:	Hugh Dickins <hughd@...gle.com>
Cc:	paulmck@...ux.vnet.ibm.com, LKML <linux-kernel@...r.kernel.org>,
	Miklos Szeredi <mszeredi@...e.cz>
Subject: Re: rcu: endless stalls

On Wed, 2012-06-13 at 07:56 +0200, Mike Galbraith wrote:

> Question remains though.  Maybe the box hit some other problem that led
> to death by RCU gripage, but the info I received indicated the box was
> in the midst of a major spin-fest.

To (maybe) speak more clearly, since it's a mutex like any other mutex
that loads of CPUs can hit if you've got loads of CPUs, did huge box
driver do something that we don't expect so many CPUs to be doing, thus
instigate simultaneous exit trouble (ie shoot self in foot), or did that
mutex addition create the exit trouble which box appeared to be having?

Too bad box RCU griped itself to death, would have been nice to have
more than a snippet.

-Mike

--
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/