linux-kernel - Re: Question about sched

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: <20190513153714.GA40957@google.com>
Date:   Mon, 13 May 2019 11:37:14 -0400
From:   Joel Fernandes <joel@...lfernandes.org>
To:     "Paul E. McKenney" <paulmck@...ux.ibm.com>
Cc:     Andrea Parri <andrea.parri@...rulasolutions.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        Juri Lelli <juri.lelli@...hat.com>,
        Morten Rasmussen <morten.rasmussen@....com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: Question about sched_setaffinity()

On Mon, May 13, 2019 at 05:20:43AM -0700, Paul E. McKenney wrote:
> 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.

The other "toy" implementation I noticed is based on reader/writer locking.

Would you see value in having that as an additional rcu torture type?

thanks,

 - Joel