On Sat, May 11, 2019 at 11:45:20PM +0200, Andrea Parri wrote:
> > > The below trace explain the issue. Some Paul person did it, see below.
> > > It's broken per construction :-)
> > 
> > *facepalm*  Hence the very strange ->cpus_allowed mask.  I really
> > should have figured that one out.
> > 
> > The fix is straightforward.  I just added "rcutorture.shuffle_interval=0"
> > to the TRIVIAL.boot file, which stops rcutorture from shuffling its
> > kthreads around.
> 
> I added the option to the file and I didn't reproduce the issue.

Thank you!  May I add your Tested-by?

                                                        Thanx, Paul

> > Please accept my apologies for the hassle, and thank you for tracking
> > this down!!!
> 
> Peter (echoing Paul):  Thank you for pointing that shuffler out!
> 
>   Andrea
> 

Reply via email to