Re: Question about sched_setaffinity()

[Paul E. McKenney]

On Sun, May 12, 2019 at 03:05:39AM +0200, Andrea Parri wrote:
> > > > 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?
> 
> Please feel free to do so.  But it may be worth to squash "the commits"
> (and adjust the changelogs accordingly).  And you might want to remove
> some of those debug checks/prints?

Revert/remove a number of the commits, but yes.  ;-)

And remove the extra loop, but leave the single WARN_ON() complaining
about being on the wrong CPU.

							Thanx, Paul