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
| ||
|
Date: Tue, 4 Oct 2016 00:06:23 -0700 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: Rich Felker <dalias@...c.org> Cc: Daniel Lezcano <daniel.lezcano@...aro.org>, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-sh@...r.kernel.org, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH v7 2/2] clocksource: add J-Core timer/clocksource driver On Mon, Oct 03, 2016 at 06:10:39PM -0400, Rich Felker wrote: > On Mon, Sep 26, 2016 at 11:27:14PM +0200, Daniel Lezcano wrote: > > On 26/09/2016 23:07, Rich Felker wrote: > > > Ping. Is there anything that still needs to be changed for this driver > > > to be acceptable? > > > > It is on my radar. I'm reviewing it. > > > > Can you elaborate the workaround mentioned in the changelog. I have been > > digging into the lkml@ thread but it is not clear if the issue is > > related to the time framework, the driver itself or whatever else. Can > > you clarify that ? > > Do you have comments on any remaining issues other than this > workaround? If not I don't mind removing the workaround and trying to > solve the issue separately later. Let me know and either way I'll > submit a v8. One question of interest to me is whether this patchset prevents the RCU CPU stall warnings that you are seeing. Thanx, Paul
Powered by blists - more mailing lists