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] [day] [month] [year] [list]
Message-ID: <20160209162427.GH16122@e104818-lin.cambridge.arm.com>
Date:	Tue, 9 Feb 2016 16:24:27 +0000
From:	Catalin Marinas <catalin.marinas@....com>
To:	Will Deacon <will.deacon@....com>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Yang Shi <yang.shi@...aro.org>, linaro-kernel@...ts.linaro.org,
	linux-rt-users@...r.kernel.org, bigeasy@...utronix.de,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: replace read_lock to rcu lock in call_step_hook

On Tue, Feb 09, 2016 at 04:04:42PM +0000, Will Deacon wrote:
> On Tue, Feb 09, 2016 at 10:07:58AM -0500, Steven Rostedt wrote:
> > On Tue, 9 Feb 2016 14:54:26 +0000
> > Will Deacon <will.deacon@....com> wrote:
> > 
> > 
> > > Acked-by: Will Deacon <will.deacon@....com>
> 
> > The patch looks good to me. Do you want to take it through your tree?
> > 
> > It benefits mainline too as a rcu_read_lock() is more efficient than
> > rwlocks. Although I will say this is a slow path anyway.
> 
> I was thinking that Catalin would queue it for 4.6 in the arm64 tree,
> since that's probably easiest in case any unlikely conflicts crop up.

Queued.

-- 
Catalin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ