linux-kernel - Re: rcu: Merge RCU-bh into RCU-preempt

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20181108160256.xpawe65h5lm65soi@linutronix.de>
Date:   Thu, 8 Nov 2018 17:02:57 +0100
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     "Paul E. McKenney" <paulmck@...ux.ibm.com>
Cc:     tglx@...utronix.de, linux-rt-users@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: rcu: Merge RCU-bh into RCU-preempt

On 2018-11-01 16:18:04 [-0700], Paul E. McKenney wrote:
> The need for this goes away as of the current merge window because
> RCU-bh has gone away.  (Aside from still being able to do things
> like rcu_read_lock_bh() as a documentation device.)

So in -RT rcu_read_lock_bh() does
 { local_bh_disable() ;  rcu_read_lock() }

So you are saying that this is also the case in v4.20?

> 							Thanx, Paul
> 

Sebastian