linux-kernel - RE: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

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: <88DC34334CA3444C85D647DBFA962C2735B0510F@SHSMSX104.ccr.corp.intel.com>
Date:   Thu, 28 Mar 2019 01:36:12 +0000
From:   "Zhang, Jun" <jun.zhang@...el.com>
To:     "paulmck@...ux.ibm.com" <paulmck@...ux.ibm.com>
CC:     "He, Bo" <bo.he@...el.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        "Xiao, Jin" <jin.xiao@...el.com>,
        "Bai, Jie A" <jie.a.bai@...el.com>
Subject: RE: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from
 softirq and interrupt

Hello, Paul

Yes, I only use original V3.18.136 to test. Because system run very slowly, I give up.

Device: NUC (made in 2017)
OS:        ubuntu 16.04
Kernel: V3.18.136 (come from https://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18.136/) 
System can boot, but run very slowly, and couldn't connect the network.
This make me not to work with terminal, because system very slowly. 
So I don’t use V3.18.136+patch to test.


-----Original Message-----
From: Paul E. McKenney [mailto:paulmck@...ux.ibm.com] 
Sent: Wednesday, March 27, 2019 23:10
To: Zhang, Jun <jun.zhang@...el.com>
Cc: He, Bo <bo.he@...el.com>; Greg Kroah-Hartman <gregkh@...uxfoundation.org>; linux-kernel@...r.kernel.org; stable@...r.kernel.org; Xiao, Jin <jin.xiao@...el.com>; Bai, Jie A <jie.a.bai@...el.com>
Subject: Re: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup from softirq and interrupt

Hello, Jun,

Do you see the same hang without the patch?

							Thanx, Paul

On Wed, Mar 27, 2019 at 01:50:57AM +0000, Zhang, Jun wrote:
> Hello，Paul
> 
> I use a new NUC (made in 2017) to test, meet the same hang. System run very slowly.
> 
> But I use my PC (made before 2015), test V3.18.136+ patch for 12 hours, still well.
> 
> Maybe V3.18.y don't support some new devices.
> 
> 
> -----Original Message-----
> From: Paul E. McKenney [mailto:paulmck@...ux.ibm.com]
> Sent: Tuesday, March 26, 2019 23:56
> To: He, Bo <bo.he@...el.com>
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>; 
> linux-kernel@...r.kernel.org; stable@...r.kernel.org; Zhang, Jun 
> <jun.zhang@...el.com>; Xiao, Jin <jin.xiao@...el.com>; Bai, Jie A 
> <jie.a.bai@...el.com>
> Subject: Re: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup 
> from softirq and interrupt
> 
> On Tue, Mar 26, 2019 at 08:43:45AM +0000, He, Bo wrote:
> > Hi, Paul:
> > 	I have tried on my PC and not hit any hang issue with RCU torture test for one hour, the configurations are like:
> > OS: ubuntu 16.04
> > kenrel: 3.18.136 + 3.18 rcu patch
> > CPU:  Intel(R) Xeon(R) CPU E3-1225 V2 @ 3.20GHz
> 
> Sounds good, please proceed!
> 
> 							Thanx, Paul
> 
> > -----Original Message-----
> > From: Paul E. McKenney <paulmck@...ux.ibm.com>
> > Sent: Tuesday, March 26, 2019 12:00 AM
> > To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > Cc: He, Bo <bo.he@...el.com>; linux-kernel@...r.kernel.org; 
> > stable@...r.kernel.org; Zhang, Jun <jun.zhang@...el.com>; Xiao, Jin 
> > <jin.xiao@...el.com>; Bai, Jie A <jie.a.bai@...el.com>
> > Subject: Re: [PATCH 3.18 132/134] rcu: Do RCU GP kthread self-wakeup 
> > from softirq and interrupt
> > 
> > On Sat, Mar 23, 2019 at 07:33:15AM +0100, Greg Kroah-Hartman wrote:
> > > On Fri, Mar 22, 2019 at 04:00:17PM +0000, He, Bo wrote:
> > > > Hi, Greg:
> > > > 	Can you hold on the 3.18-stable branch, it seems there are some issue, please see the comments from Paul:
> > > > 
> > > > Comments from Paul:
> > > > I subjected all of the others to light rcutorture testing, which 
> > > > they passed.  This v3.18 patch hung, however.  Trying it again 
> > > > with stock
> > > > v3.18 got the same hang, so I believe we can exonerate the patch and give it a good firm "maybe" on 3.18.
> > > > 
> > > > Worth paying special attention to further test results from 3.18.x, though!
> > > 
> > > Ok, I've dropped this from the 3.18.y queue now, thanks.
> > 
> > Bo, if you know of a "y" for 3.18.y that would likely pass rcutorture testing, please let me know.
> > 
> > 							Thanx, Paul
> > 
>