linux-kernel - Re: rcu: endless stalls

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: <1339558508.7472.26.camel@marge.simpson.net>
Date:	Wed, 13 Jun 2012 05:35:08 +0200
From:	Mike Galbraith <efault@....de>
To:	paulmck@...ux.vnet.ibm.com
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Miklos Szeredi <mszeredi@...e.cz>,
	Hugh Dickins <hughd@...gle.com>
Subject: Re: rcu: endless stalls

On Mon, 2012-06-11 at 20:10 +0200, Mike Galbraith wrote: 
> On Mon, 2012-06-11 at 11:01 -0700, Paul E. McKenney wrote: 

> > > 2aa15890 - mm: prevent concurrent unmap_mapping_range() on the same inode
> > 
> > I confess, you lost me on this one.  You believe that this commit is
> > the cause of the RCU CPU stall warnings?
> 
> 4096 tasks on 4096 CPUs exit (well, try to) simultaneously.
> 
> Call Trace:
>                 __mutex_lock_slowpath+0x94/0x150
>                 mutex_lock+0x1a/0x40
>                 unlink_file_vma+0x3f/0xf0
>                 free_pgtables+0x40/0x100
>                 exit_mmap+0xb0/0x120
>                 mmput+0x49/0x120
>                 exit_mm+0x122/0x160
>                 do_exit+0x179/0x8d0
>                 do_group_exit+0x3d/0xb0
>                 sys_exit_group+0x12/0x20
> 
> Monster box dies screaming.

That commit landed in stable, box with way too many cores (NR_CPUS=0!!)
chokes instantly with loads of spinners.  Ok, so zillion CPUs grabbing a
mutex in lockstep is a bad idea (_having_ zillion?), but is there pilot
error involved in a logjam like this?

-Mike

--
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/