linux-kernel - Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in process

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]

Date:	Wed, 30 Sep 2015 02:25:53 +0200
From:	Zdenek Kaspar <zkaspar82@...il.com>
To:	Andre Tomt <andre@...t.net>, Julian Anastasov <ja@....bg>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>, stable@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Stephen Hemminger <stephen@...workplumber.org>,
	holger.hoffstaette@...glemail.com
Subject: Re: [PATCH 4.1 125/159] net: call rcu_read_lock early in
 process_backlog

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/