linux-kernel - Re: [PATCH -mm 1/3] proc: get_nr_threads() doesn't need ->siglock any longer

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] [day] [month] [year] [list]

Message-Id: <20100409194853.95D09BD02@magilla.sf.frob.com>
Date:	Fri,  9 Apr 2010 12:48:53 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexey Dobriyan <adobriyan@...il.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm 1/3] proc: get_nr_threads() doesn't need ->siglock any
	longer

Acked-by: Roland McGrath <roland@...hat.com>

I'm not entirely sure about the name, but it's probably fine.  There should
be some comments somewhere making clear what "nr" or kind of threads this
refers to.  This is threads created and not yet reaped.  It differs from
the "threads not yet exited" (signal->live) count only during some races
around exit time, and when ptrace is preventing self-reaping.

Thanks,
Roland
--
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/