linux-kernel - Re: [PATCH RT] time/hrtimer: disable that mode check

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20171213114956.64ceddf6@gandalf.local.home>
Date:   Wed, 13 Dec 2017 11:49:56 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        linux-rt-users@...r.kernel.org, linux-kernel@...r.kernel.org,
        tglx@...utronix.de
Subject: Re: [PATCH RT] time/hrtimer: disable that mode check

On Wed, 13 Dec 2017 15:22:57 +0100
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:

> On 2017-12-13 15:19:19 [+0100], Peter Zijlstra wrote:
> > On Wed, Dec 13, 2017 at 02:58:35PM +0100, Sebastian Andrzej Siewior wrote:  
> > > On -RT we push all timers by default into the soft-mode. The
> > > "start/update" code does not use that SOFT bit so we always see that
> > > warning.  
> > 
> > Not _all_ timers I hope? There's a few the scheduler and perf use that
> > really should stay in hardirq context.  
> That is correct, a few ones remain in the hardirq context.
> 

As Sebastian said, by default they are in SOFT mode. I'm assuming the
ones that are not have some logic to make sure they are not in SOFT
mode.

-- Steve