From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f170.google.com ([209.85.212.170]:36763 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752009AbbI3AZ4 (ORCPT ); Tue, 29 Sep 2015 20:25:56 -0400 Subject: Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog To: Andre Tomt , Julian Anastasov , Greg Kroah-Hartman References: <20150926205313.363686083@linuxfoundation.org> <20150926205320.865002695@linuxfoundation.org> <5609F377.2090905@tomt.net> <560A4E3A.2080104@tomt.net> <560A661C.7000406@tomt.net> <560A6C8B.7080105@tomt.net> Cc: linux-kernel@vger.kernel.org, "David S. Miller" , stable@vger.kernel.org, "Eric W. Biederman" , Stephen Hemminger , holger.hoffstaette@googlemail.com From: Zdenek Kaspar Message-ID: <560B2C11.2020907@gmail.com> Date: Wed, 30 Sep 2015 02:25:53 +0200 MIME-Version: 1.0 In-Reply-To: <560A6C8B.7080105@tomt.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org List-ID: On 09/29/2015 12:48 PM, Andre Tomt wrote: > On 29. sep. 2015 12:21, Andre Tomt wrote: >> Meanwhile I'll revert both the mentioned net patches and see how it goes. > > So that blew up as well, meaning it's not any of these two patches: > [PATCH 4.1 124/159] net: do not process device backlog during unregistration > [PATCH 4.1 125/159] net: call rcu_read_lock early in process_backlog > > I'll be offline for a half+ day, I'll look into bisecting when back if > nobody has figured it out by then. After I noticed your crash I did ran some tests with 4.1.9 on physical host (old core2duo) with kvm guest.. nfs client/server between guest/host + X on guest, next kvm guest to force host to swap some memory to create memory pressure and all this with 'perf top' on host machine without any problems.. HTH, Z.