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  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]
Date:	Thu, 23 Oct 2014 12:52:21 -0700
From:	"Paul E. McKenney" <>
To:	Dave Jones <>,
	Linux Kernel <>,,
Subject: Re: rcu_preempt detected stalls.

On Thu, Oct 23, 2014 at 03:37:59PM -0400, Dave Jones wrote:
> On Thu, Oct 23, 2014 at 12:28:07PM -0700, Paul E. McKenney wrote:
>  > >  > This one will require more looking.  But did you do something like
>  > >  > create a pair of mutually recursive symlinks or something?  ;-)
>  > > 
>  > > I'm not 100% sure, but this may have been on a box that I was running
>  > > tests on NFS. So maybe the server had disappeared with the mount
>  > > still active..
>  > > 
>  > > Just a guess tbh.
>  > 
>  > Another possibility might be that the box was so overloaded that tasks
>  > were getting preempted for 21 seconds as a matter of course, and sometimes
>  > within RCU read-side critical sections.  Or did the box have ample idle
>  > time?
> I fairly recently upped the number of child processes I typically run
> with, so it being overloaded does sound highly likely.

Ah, that could do it!  One way to test extreme loads and not trigger
RCU CPU stall warnings might be to make all of your child processes all
sleep during a given interval of a few hundred milliseconds during each
ten-second interval.  Would that work for you?

							Thanx, Paul

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists