linux-kernel - Re: [mminit] [ INFO: possible recursive locking detected ]

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:	Thu, 16 Jul 2015 18:51:39 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	Konstantin Khlebnikov <koct9i@...il.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>, nicstange@...il.com,
	Linux Memory Management List <linux-mm@...ck.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	LKP <lkp@...org>
Subject: Re: [mminit] [ INFO: possible recursive locking detected ]

On Thu, Jul 16, 2015 at 08:13:38PM +0300, Konstantin Khlebnikov wrote:
> > @@ -1187,14 +1195,14 @@ void __init page_alloc_init_late(void)
> >  {pgdat_init_rwsempgdat_init_rwsempgdat_init_rwsem
> >         int nid;
> >
> > +       /* There will be num_node_state(N_MEMORY) threads */
> > +       atomic_set(&pgdat_init_n_undone, num_node_state(N_MEMORY));
> >         for_each_node_state(nid, N_MEMORY) {
> > -               down_read(&pgdat_init_rwsem);
> 
> Rw-sem have special "non-owner" mode for keeping lockdep away.
> This should be enough:
> 

I think in this case that the completions look nicer though so I think
I'll keep them.

-- 
Mel Gorman
SUSE Labs
--
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/